Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clone already referenced & No XPathResult namespace #72

Open
fgiasson opened this issue Jul 9, 2014 · 7 comments
Open

Clone already referenced & No XPathResult namespace #72

fgiasson opened this issue Jul 9, 2014 · 7 comments

Comments

@fgiasson
Copy link

fgiasson commented Jul 9, 2014

I just started testing Domina, and as soon as I compile it using lein cljsbuild once I am getting the following warnings:

Compiling "resources/public/test.js" from ["src/cljs"]...
WARNING: clone already refers to: /clone being replaced by: domina/clone at line
 147 file:/C:/Users/Proprietaire/.m2/repository/domina/domina/1.0.2/domina-1.0.2
.jar!/domina.cljs
WARNING: No such namespace: XPathResult at line 30 file:/C:/Users/Proprietaire/.
m2/repository/domina/domina/1.0.2/domina-1.0.2.jar!/domina/xpath.cljs
WARNING: No such namespace: XPathResult at line 41 file:/C:/Users/Proprietaire/.
m2/repository/domina/domina/1.0.2/domina-1.0.2.jar!/domina/xpath.cljs

The XPathResult warning appears when I include xpath: [domina.xpath :only [xpath]]

I use the latest ClojureScript. I did some reasearch and I haven't found anything regarding this issue, so I am wondering if it is my setup that is wrong or an actual issue with Domina.

@sritchie
Copy link

hey @levand, any update on this? Also, do you guys have a scheduled time for a next release? I see another pull req was merged that kills that "/clone" warning.

Thanks!

@eagleflo
Copy link

Both of these issues have been fixed in the master, but no new release has been made. Also, the clone fix hasn't been picked up by 1.0.3-SNAPSHOT.

Maybe it's time to release 1.0.3?

@magomimmo
Copy link
Contributor

+1.
I agree it's time to release 1.0.3.

@ckirkendall
Copy link
Collaborator

I will see if I can't push a new one out today.

@magomimmo
Copy link
Contributor

Thanks @ckirkendall

@ocharles
Copy link

Any update on this? I'm also seeing these warnings in our builds.

@karneaud
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants