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/22 23:30:52 UTC

[jira] (MSHADE-145) Site not generated correctly when overriding dependencyReducedPomLocation with relocation

Anthony Whitford created MSHADE-145:
---------------------------------------

             Summary: Site not generated correctly when overriding dependencyReducedPomLocation with relocation
                 Key: MSHADE-145
                 URL: https://jira.codehaus.org/browse/MSHADE-145
             Project: Maven 2.x Shade Plugin
          Issue Type: Bug
    Affects Versions: 2.0
         Environment: Windows XP, Java 6 Update 24, Maven 3.0.4
            Reporter: Anthony Whitford
         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 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