[
http://jira.codehaus.org/browse/MEXEC-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112962
]
Holger Hoffstätte commented on MEXEC-38:
----------------------------------------
Attaching the relevant portion of the log since our Bamboo logs will expire
sooner or later:
01-Nov-2007 07:57:57 [INFO]
------------------------------------------------------------------------
01-Nov-2007 07:57:57 [INFO] Error for project: Full Distribution (during
install)
01-Nov-2007 07:57:57 [INFO]
------------------------------------------------------------------------
01-Nov-2007 07:57:57 [INFO] Failed to resolve artifact.
01-Nov-2007 07:57:57
01-Nov-2007 07:57:57 Missing:
01-Nov-2007 07:57:57 ----------
01-Nov-2007 07:57:57 1) org.codehaus.mojo.groovy:groovy-mojo-common:jar:2.4.1
01-Nov-2007 07:57:57
01-Nov-2007 07:57:57 Try downloading the file manually from the project
website.
01-Nov-2007 07:57:57
01-Nov-2007 07:57:57 Then, install it using the command:
01-Nov-2007 07:57:57 mvn install:install-file
-DgroupId=org.codehaus.mojo.groovy -DartifactId=groovy-mojo-common \
01-Nov-2007 07:57:57 -Dversion=2.4.1 -Dpackaging=jar
-Dfile=/path/​to/​file
01-Nov-2007 07:57:57 Alternatively, if you host your own repository you can
deploy the file there: mvn deploy:deploy-file
-DgroupId=org.codehaus.mojo.groovy -DartifactId=groovy-mojo-common \
01-Nov-2007 07:57:57 -Dversion=2.4.1 -Dpackaging=jar
-Dfile=/path/​to/​file \
01-Nov-2007 07:57:57 -Durl=[url] -DrepositoryId=[id]
01-Nov-2007 07:57:57
01-Nov-2007 07:57:57 Path to dependency:
01-Nov-2007 07:57:57 1)
org.codehaus.mojo.groovy:groovy-maven-plugin:maven-plugin:1.0-beta-2
01-Nov-2007 07:57:57 2)
org.codehaus.mojo.groovy:groovy-mojo-common:jar:2.4.1
01-Nov-2007 07:57:57
01-Nov-2007 07:57:57 2)
org.codehaus.mojo.groovy:groovy-plexus-factory:jar:2.4.1
01-Nov-2007 07:57:57
01-Nov-2007 07:57:57 Try downloading the file manually from the project
website.
01-Nov-2007 07:57:57
01-Nov-2007 07:57:57 Then, install it using the command:
01-Nov-2007 07:57:57 mvn install:install-file
-DgroupId=org.codehaus.mojo.groovy -DartifactId=groovy-plexus-factory \
01-Nov-2007 07:57:57 -Dversion=2.4.1 -Dpackaging=jar
-Dfile=/path/​to/​file
01-Nov-2007 07:57:57 Alternatively, if you host your own repository you can
deploy the file there: mvn deploy:deploy-file
-DgroupId=org.codehaus.mojo.groovy -DartifactId=groovy-plexus-factory \
01-Nov-2007 07:57:57 -Dversion=2.4.1 -Dpackaging=jar
-Dfile=/path/​to/​file \
01-Nov-2007 07:57:57 -Durl=[url] -DrepositoryId=[id]
01-Nov-2007 07:57:57
01-Nov-2007 07:57:57 Path to dependency:
01-Nov-2007 07:57:57 1)
org.codehaus.mojo.groovy:groovy-maven-plugin:maven-plugin:1.0-beta-2
01-Nov-2007 07:57:57 2)
org.codehaus.mojo.groovy:groovy-plexus-factory:jar:2.4.1
01-Nov-2007 07:57:57
01-Nov-2007 07:57:57 ----------
01-Nov-2007 07:57:57 2 required artifacts are missing.
01-Nov-2007 07:57:57
Obviously there is no groovy-plexus-factory:jar:2.4.1 *anywhere*; the
referenced $version is a wrongly resolved property.
> ${version} being set?
> ---------------------
>
> Key: MEXEC-38
> URL: http://jira.codehaus.org/browse/MEXEC-38
> Project: Maven 2.x Exec Plugin
> Issue Type: Bug
> Affects Versions: 1.1-beta-1
> Reporter: andrew cooke
>
> ok, apologies in advance - this isn't going to be a very helpful report - i
> did try to make a small "demo" test case, but failed, and i don't fully
> understand the issues. but here goes...
> i added a sub-project to the mule build that uses the maven-exec-plugin.
> unfortunately, when this was enabled along with another profile the build
> failed with reports of missing versions of packages that never existed.
> you can see a failure report here:
> http://dev.mulesource.com/bamboo/browse/MULE-V2X-670
> in the log at http://dev.mulesource.com/bamboo/browse/MULE-V2X-670/log you
> can see that there are a bunch of errors due to missing packages with version
> 2.4.1 - those packages do not exist. the version number is bogus.
> the package itself can be seen here:
> http://cvs.codehaus.org/browse/mule/branches/mule-2.x/tools/schemadocs
> some more experimenting showed that what seems to be happening is that when
> poms are pulled in from the repo and they contain ${version}, the value of
> version is being set to some random value by the exec plugin (you can check
> this by editing the pom in the repo and replacing the ${version} with the
> correct value - the associated error then goes away).
> our workaround was to add fake dependencies so that the sub-project using the
> plugin comes last (or at least later) in the build.
> i also found this report, which seems similar:
> http://jira.codehaus.org/browse/MNGECLIPSE-30
> your best chance at duplicating is probably to check mule out from svn,
> remove the dependencies at the top of the schemadocs pom (that refer to
> distributions) and running "mvn -Pdistributions,schemadocs install" (the
> profiles just enable the appropriate sub-packages).
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
