[
https://jira.codehaus.org/browse/MSHADE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301765#comment-301765
]
Benson Margulies commented on MSHADE-123:
-----------------------------------------
OK, I see how this happens. The question is going to be how to fix it.
The d-r-p becomes 'the pom', and its location is now in target to avoid build
collisions, but now basedir tracks it. I believe I can fix this by fixing the
basedir for the d-r-p model.
> 1.7 Causes failures in other plugins make "basedir" point to the build dir
> --------------------------------------------------------------------------
>
> Key: MSHADE-123
> URL: https://jira.codehaus.org/browse/MSHADE-123
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Reporter: Shay Banon
> Assignee: Benson Margulies
> Priority: Blocker
> Attachments: mvn-shade.zip
>
>
> Upgrading the 1.7 causes other plugins to have basedir now pointing to build
> dir, or something similar. The attached test case shows that with shade
> plugin 1.5, the assembly plugins successfully finds the sample.txt file (in
> basedir), while upgrading to 1.7 shade plugin causes the assembly plugin not
> to find it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
