Updating project POM via project.setFile(..) changes project basedir, and
project classpath when used as a dependency in a reactor
----------------------------------------------------------------------------------------------------------------------------------
Key: MNG-3693
URL: http://jira.codehaus.org/browse/MNG-3693
Project: Maven 2
Issue Type: Bug
Components: POM, Reactor and workspace
Affects Versions: 2.0.10
Reporter: John Casey
When a reactor build contains an interproject dependency, and the dependency
project's build switches the project's POM file, the dependent project may get
the wrong classpath for the dependency project as long as it references
${basedir}/target/classes.
For example, the shade plugin produces a dependency-reduced POM, and sets it on
the project instance using project.setFile(..). This act reorients the
project's basedir according to the new POM, which can return the wrong location
for the build.outputDirectory (since this is now based on build.directory,
which is now based on basedir).
--
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
