maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne (JIRA)" <j...@codehaus.org>
Subject [jira] (MSITE-691) Aggregator pom with child parent not handled
Date Mon, 03 Jun 2013 14:08:03 GMT
Stephen Colebourne created MSITE-691:
----------------------------------------

             Summary: Aggregator pom with child parent not handled
                 Key: MSITE-691
                 URL: https://jira.codehaus.org/browse/MSITE-691
             Project: Maven 2.x and 3.x Site Plugin
          Issue Type: Bug
          Components: multi module
    Affects Versions: 3.3
            Reporter: Stephen Colebourne
         Attachments: OG-Platform.zip

The attached zip demonstrates a project where the parent is an aggregator only pom and the
children include the parent:

{code}
platform
- pom.xml  (aggregator only)
- projects
  - parent
    - pom.xml  (parent for the child project)
  - child
    - pom.xml
{code}

Running the zip file with "mvn clean test site" will build incorrect hyperlinks.

The top left hyperlinks, added by the site plugin, are defined as "parent/index.html" and
"child/child/index.html". I consider the former to be correct, but not the latter.

In addition, the navigation links produce both a link to the parent (under the "Parent Project"
heading), and a second link to the parent under the "Modules" heading. This seems unnecessary,
and in fact does not work in design terms, see below. (It appears that separate aggregator
and parent pom projects are not really supported in design terms)

The child projects also contain the wrong link to the parent (under "Parent Projects" in the
navigation area). They create a link as "../../parent/index.html". This will be one ".." too
far, as the "distributionManagement.site.url" definition removes the extra level.

Finally, the site of the parent pom does not contain a "Parent projects" link in the navigation
area. That would make sense if there was no aggregator project, but does not make sense here
from a website pint of view.

What I would expect is the following staged website:
{code}
target
- staging
  - index.html  (links to child projects, including parent)
  - parent 
    - index.html  (link back to aggregator)
  - child
    - index.html  (link back to aggregator, link to parent: "../parent/index.html")
{code}



--
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

Mime
View raw message