Closed GoogleCodeExporter closed 9 years ago
Have the same behaviour on windows, both with Maven 3.0.1 and 3.0.2.
Andreas
Original comment by andreas....@gmail.com
on 21 Jan 2011 at 11:55
Also breaks on my MacOSX 10.6.6 machine using Maven 3.0.1 and Java6 :-(
Original comment by justbee...@googlemail.com
on 25 Jan 2011 at 12:39
I have the same issue, but with easyb version 1.1 on Windows 7.
Maven 3.0.1
easyb-core 1.1
maven-easyb-plugin 1.1
when the plugin runs the following error & warning messages are displayed:
[WARNING] Missing POM for org.easyb:easyb-core:jar:1.1
[ERROR] Missing:
[ERROR] ----------
[ERROR] 1) org.easyb:easyb-core:jar:1.1
...
[ERROR] Path to dependency:
[ERROR] 1) org.easyb:maven-easyb-plugin:jar:1.1
[ERROR] 2) org.easyb:easyb-core:jar:1.1
I also have easyb-core 1.1 in my pom's dependencies, and it resolves fine there.
Original comment by peter.ba...@gmail.com
on 2 Apr 2011 at 12:56
I tried the exact same pom.xml that I mentioned in my previous comment (3) with
Maven 2.2.1 and it works flawlessly. So this looks like it is some kind of
incompatibility with Maven 3
Original comment by peter.ba...@gmail.com
on 2 Apr 2011 at 1:22
Have you tried it with Maven 3.0.3? The maven team won't support issues with
3.0.1. I did all of the integration testing and releasing using 3.0.3.
Original comment by richard....@gmail.com
on 2 Apr 2011 at 7:51
Hi Richard, I tried it with Maven 3.0.3, but still have same problem. I'll
attach my pom file. Maybe I have an incorrect Groovy setup?
(the parent pom is just an empty shell with references to 2 modules, there
aren't any dependencies or configuration shared between modules at this time)
Original comment by peter.ba...@gmail.com
on 3 Apr 2011 at 8:45
Attachments:
I have also just tried to reproduce the problem I had using Maven 3.0.3 on
MacOS.
** I cleaned up the local Maven cache completely and got the error again. **
Puzzling that I see this warning:
[DEBUG] org.easyb:maven-easyb-plugin:jar:0.9.7-1 (selected for null)
[DEBUG] Verifying availability of
/Users/jki/.m2/repository/org/easyb/easyb/0.9.7/easyb-0.9.7.pom from []
[WARNING] Missing POM for org.easyb:easyb:jar:0.9.7: Error resolving project
artifact: Could not find artifact org.easyb:easyb:pom:0.9.7 for project
org.easyb:easyb:pom:0.9.7
[DEBUG] org.easyb:easyb:jar:0.9.7:compile (selected for compile)
[DEBUG] Verifying availability of
/Users/jki/.m2/repository/org/easyb/easyb/0.9.7/easyb-0.9.7.jar from []
As before I can verify that the easyb plugin
(org.easyb:maven-easyb-plugin:jar:0.9.7-1) that is supposed to be missing, is
indeed available my local Maven cache.
Original comment by justbee...@googlemail.com
on 4 Apr 2011 at 6:01
Peter, with your attached pom, I had to remove the parent as you didn't include
it, but a mvn dependency:tree gives this:
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ fctr-test ---
[INFO] com.streamhead:fctr-test:jar:0.0.1-SNAPSHOT
[INFO] +- org.codehaus.geb:geb-core:jar:0.5.1:compile
[INFO] | \- org.seleniumhq.selenium:selenium-common:jar:2.0a7:compile
[INFO] +- org.seleniumhq.selenium:selenium-firefox-driver:jar:2.0b1:compile
[INFO] | +- org.seleniumhq.selenium:selenium-remote-client:jar:2.0b1:compile
[INFO] | | +- cglib:cglib-nodep:jar:2.1_3:compile
[INFO] | | +- org.seleniumhq.selenium:selenium-remote-common:jar:2.0b1:compile
[INFO] | | | +- org.json:json:jar:20080701:compile
[INFO] | | | +- commons-codec:commons-codec:jar:1.4:compile
[INFO] | | | \- com.google.guava:guava:jar:r07:compile
[INFO] | | \- org.apache.httpcomponents:httpclient:jar:4.0.2:compile
[INFO] | | +- org.apache.httpcomponents:httpcore:jar:4.0.1:compile
[INFO] | | \- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] | \- commons-io:commons-io:jar:1.4:compile
[INFO] +- org.codehaus.groovy:groovy-all:jar:1.7.10:compile
[INFO] +- org.codehaus.gmaven.runtime:gmaven-runtime-1.7:jar:1.3:compile
[INFO] | +- org.slf4j:slf4j-api:jar:1.5.10:compile
[INFO] | +- org.codehaus.gmaven.feature:gmaven-feature-support:jar:1.3:compile
[INFO] | | \- org.codehaus.gmaven.feature:gmaven-feature-api:jar:1.3:compile
[INFO] | +- org.codehaus.gmaven.runtime:gmaven-runtime-support:jar:1.3:compile
[INFO] | | +- org.codehaus.gmaven.runtime:gmaven-runtime-api:jar:1.3:compile
[INFO] | | +- org.sonatype.gshell:gshell-io:jar:2.0:compile
[INFO] | | | \- org.sonatype.gossip:gossip:jar:1.0:compile
[INFO] | | +- org.codehaus.plexus:plexus-utils:jar:2.0.1:compile
[INFO] | | \- com.thoughtworks.qdox:qdox:jar:1.10:compile
[INFO] | +- org.apache.ant:ant:jar:1.8.1:compile
[INFO] | | \- org.apache.ant:ant-launcher:jar:1.8.1:compile
[INFO] | \- jline:jline:jar:0.9.94:compile
[INFO] | \- junit:junit:jar:3.8.1:compile
[INFO] \- org.codehaus.geb:geb-easyb:jar:0.5.1:compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 28.183s
[INFO] Finished at: Mon Apr 04 22:04:02 NZST 2011
[INFO] Final Memory: 6M/81M
[INFO] ------------------------------------------------------------------------
mvn verify runs fine as well
Original comment by richard....@gmail.com
on 4 Apr 2011 at 10:05
jkind... please change to 1.1 for support, we want to push people away from the
old numbering schemes.
Original comment by richard....@gmail.com
on 4 Apr 2011 at 10:06
i have now been able to duplicate this problem and am working on it.
Original comment by richard%...@gtempaccount.com
on 7 Apr 2011 at 8:45
with John Smart's help, I found the problem. There is an incompatibility
between Aether and the API that the easyb-maven-plugin uses to find artifacts.
Ideally we shouldn't be using the Ant plugin to run the easyb one, so I'll tap
Jeff and let him know I'll be changing this.
Original comment by richard%...@gtempaccount.com
on 7 Apr 2011 at 11:32
Any progress on that issue ?
I have exactly the same issue on Windows 7, with maven-easyb-plugin 1.1 and
Maven 3.0.3
Original comment by lke...@gmail.com
on 19 May 2011 at 11:06
This issue should now be solved with the 1.2 easyb maven plugin. please change
versions and retest. i'll mark this fixed
Original comment by richard....@gmail.com
on 25 May 2011 at 12:16
Works perfectly now.
Thank you very much!
Original comment by peter.ba...@gmail.com
on 29 May 2011 at 1:10
Original issue reported on code.google.com by
benedict...@gmail.com
on 11 Jan 2011 at 1:35Attachments: