You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/03/03 14:31:18 UTC

[jira] [Commented] (MSHADE-123) 1.7 Causes failures in other plugins make "basedir" point to the build dir

    [ https://issues.apache.org/jira/browse/MSHADE-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177809#comment-15177809 ] 

Maximilian Michels commented on MSHADE-123:
-------------------------------------------

Same here with maven-shade-plugin 2.4.1

> 1.7 Causes failures in other plugins make "basedir" point to the build dir
> --------------------------------------------------------------------------
>
>                 Key: MSHADE-123
>                 URL: https://issues.apache.org/jira/browse/MSHADE-123
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)