You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/18 11:41:01 UTC

[jira] [Updated] (MSHADE-170) Outstanding questions about MSHADE-124

     [ https://issues.apache.org/jira/browse/MSHADE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold updated MSHADE-170:
-----------------------------------------
    Priority: Minor  (was: Major)

> Outstanding questions about MSHADE-124
> --------------------------------------
>
>                 Key: MSHADE-170
>                 URL: https://issues.apache.org/jira/browse/MSHADE-170
>             Project: Maven Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Gili
>            Priority: Minor
>             Fix For: backlog
>
>
> MSHADE-124 is marked as fixed but as Anthony Whitford points out:
> # If this is fixed, why does the documentation still warn about this? http://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#dependencyReducedPomLocation
> # Shouldn't the default location be under project.build.directory instead of basedir? Then {{mvn clean}} would be more effective, and the {{Maven Release}} plugin wouldn't give an error saying, "Cannot prepare the release because you have local modifications."



--
This message was sent by Atlassian Jira
(v8.3.4#803005)