You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anthony Whitford (JIRA)" <ji...@codehaus.org> on 2013/04/05 03:25:52 UTC

[jira] (MSHADE-124) Need better plan for getting dependency-reduced-pom.xml out of basedir

    [ https://jira.codehaus.org/browse/MSHADE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323237#comment-323237 ] 

Anthony Whitford commented on MSHADE-124:
-----------------------------------------

If this was fixed, why does the documentation still warn about this?

See:  http://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#dependencyReducedPomLocation
                
> Need better plan for getting dependency-reduced-pom.xml out of basedir
> ----------------------------------------------------------------------
>
>                 Key: MSHADE-124
>                 URL: https://jira.codehaus.org/browse/MSHADE-124
>             Project: Maven 2.x Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 1.7.1
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 2.0
>
>
> MSHADE-123 reported that putting the d-r-p into some location other
> than 'basedir' causes 'basedir' to follow it around, which can break builds.
> This is hard to fix, given the core maven definition of basedir as 'the dir containing the pom' with no option to change it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira