[
http://jira.codehaus.org/browse/MEXEC-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Lacoste closed MEXEC-38.
-------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: future)
1.1-beta-1
Closed as both me and the reporter cannot reproduce it. I expect the problem to
be outside the plugin anyway. Feel free to reopen if the problem happens again.
Thanks for your time.
> ${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
> Fix For: 1.1-beta-1
>
> Attachments: MULE-V2X-670-console-log.txt
>
>
> 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
