[ https://jira.codehaus.org/browse/MSHADE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306610#comment-306610 ]
Hung Huynh commented on MSHADE-123: ----------------------------------- I just got hit by this bug using maven-shade-plugin 1.7.1 and maven-assembly-plugin 2.3. References to ${basedir} in assembly plugin configuration file are all wrong. > 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 > Fix For: 1.7.1 > > 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