[
https://jira.codehaus.org/browse/MSHADE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345598#comment-345598
]
Gili commented on MSHADE-170:
-----------------------------
Also, I don't think MSHADE-124 is really fixed. In my own project I see this
output:
{code}
Dependency-reduced POM written at:
C:\Users\Gili\Documents\foo\backend\dependency-reduced-pom.xml
Dependency-reduced POM written at:
C:\Users\Gili\Documents\foo\backend\dependency-reduced-pom.xml
{code}
The file is written twice to the same directory, in contradiction to the
documentation which says {{The reduced POM will be named
dependency-reduced-pom.xml and is stored into the same directory as the shaded
artifact. Unless you also specify dependencyReducedPomLocation, the plugin will
create a temporary file named dependency-reduced-pom.xml in the project
basedir.}} This documentation leads me to believe that one of the files should
get written to {{$\{project.build.directory\}}}.
> Outstanding questions about MSHADE-124
> --------------------------------------
>
> Key: MSHADE-170
> URL: https://jira.codehaus.org/browse/MSHADE-170
> Project: Maven Shade Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Gili
>
> 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
(v6.1.6#6162)
