[ http://jira.codehaus.org/browse/MOJO-63?page=all ]

Brett Porter updated MOJO-63:
-----------------------------

    Component: Project Admin

> Unresolved dependencies when trying to compile Mojo revision 602 using Maven 
> 2 beta 2
> -------------------------------------------------------------------------------------
>
>          Key: MOJO-63
>          URL: http://jira.codehaus.org/browse/MOJO-63
>      Project: Mojo
>         Type: Bug

>   Components: Project Admin
>  Environment: Maven 2 beta 2
> Mojo revision 601
>     Reporter: Martin Desruisseaux
>     Assignee: Corridor Software Developer
>     Priority: Blocker

>
>
> (Note: I understand that workaround exist - compile Maven 2 from SVN with 
> -SNAPSHOT versions, or change the dependencies in Mojo's pom.xml files 
> ourself. So the "blocker" priority may be exagerate - please kick it down if 
> appropriate. I choosed the "blocker" priority from the point of view of an 
> user wanting to build Mojo using directly Maven 2-beta-2 binaries. Right now, 
>  some modules fail to compile).
> A fresh checkout of Mojo (revision 602) does not compile with Maven 2 beta 2. 
> Some pom.xml files have dependencies toward "foo-beta-1-SNAPSHOT.jar" files, 
> which don't seem to appear in the repositories listed in the parent pom.xml 
> file. Replacing "foo-beta-1-SNAPSHOT.jar" by "foo-beta-2.jar" solve the 
> problem for some plugins. More specifically, I failed to compile the 
> following modules:
> maven-commons-attributes-plugin
> Reason: Compilation failure
> package org.apache.maven.plugin does not exist
> maven-hibernate-plugin
> Root Cause: Unable to download the artifact from any repository
> GroupId: javax.transaction
> ArtifactId: jta
> Version: 1.0.1B
> Type: jar
> maven-jalopy-plugin
> Root Cause: Unable to download the artifact from any repository
> GroupId: org.apache.maven
> ArtifactId: maven-plugin-api
> Version: 2.0-beta-1-SNAPSHOT
> Type: jar
> javacc-maven-plugin
> Root Cause: Unable to download the artifact from any repository
> GroupId: org.apache.maven
> ArtifactId: maven-project
> Version: 2.0-beta-1-SNAPSHOT
> Type: jar
> maven-jdepend-plugin
> Root Cause: Unable to download the artifact from any repository
> GroupId: org.apache.maven.reporting
> ArtifactId: maven-reporting-api
> Version: 2.0-beta-1-SNAPSHOT
> Type: jar
> maven-jdiff-plugin
> Root Cause: Unable to download the artifact from any repository
> GroupId: org.apache.maven.scm
> ArtifactId: maven-scm-provider-svn
> Version: 1.0-alpha-2-SNAPSHOT
> Type: jar
> maven-jetty-plugin
> Reason: Compilation failure
> package org.apache.maven.plugin does not exist
> I will stop there, but other modules fail to compile too. A workaround is to 
> edit the pom.xml file ourself, but it would be nice if the work could be done 
> only once by a SVN commiter.
> Thanks for yours work.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to