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

Alexander Kriegisch commented on MSHADE-145:
--------------------------------------------

Besides, I agree with [~awhitford] that the build directory should be the 
default for the DRP. Otherwise we need a custom Maven Clean action plus 
specific entried in {{.gitignore}} in order to have a fairly clean project 
without warnings of newly added XML files, maybe accidentally committing them 
to the SCM. Even if that does not happen, it is simply annoying.

> Site not generated correctly when overriding dependencyReducedPomLocation 
> with relocation
> -----------------------------------------------------------------------------------------
>
>                 Key: MSHADE-145
>                 URL: https://issues.apache.org/jira/browse/MSHADE-145
>             Project: Maven Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: Windows XP, Java 6 Update 24, Maven 3.0.4
>            Reporter: Anthony Whitford
>            Priority: Major
>         Attachments: shade-site-bug.zip
>
>
> My release failed because the project uses the {{maven-shade-plugin}} and it 
> generated a {{dependency-reduced-pom.xml}} in the {{basedir}}, so the release 
> plugin complains that there are local, uncommitted modifications.
> To get my release working, I overrode the {{dependencyReducedPomLocation}} 
> configuration parameter to place it in {{project.build.directory}}:
> {code:xml}
> <configuration>
>   
> <dependencyReducedPomLocation>${project.build.directory}/dependency-reduced-pom.xml</dependencyReducedPomLocation>
>   ...
> </configuration>
> {code}
> My release worked, but then I noticed that this had a nasty side effect:  my 
> site was not generated properly!
> The project has {{src\site}} with a {{site.xml}} and APT pages.  Those were 
> no longer generated...  I have no idea how one thing is connected to the 
> other, but I did prove it by creating a sample application that illustrates 
> the problem.
> Note that the problem seems to a combination of at least 2 things:
> * {{dependencyReducedPomLocation}}
> * {{relocations}}
> In other words, if you comment out the {{dependencyReducedPomLocation}} or 
> the {{relocations}}, you can see the site being generated correctly.  But if 
> you have these, then the site will NOT generate properly.
> To be clear, the site generation is incorrect if you don't see the menu 
> layout like:
> * About
> ** Introduction 
> ** Usage 
> * Project Documentation
> * Project Information 
> A broken site, you will notice that the About menu and Usage page do not 
> exist, for example.



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

Reply via email to