maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lennart Jörelid (JIRA) <>
Subject [jira] (MSITE-669) site:stage creates incorrect structure when module paths contains sets of "../"
Date Tue, 18 Dec 2012 04:07:14 GMT


Lennart Jörelid updated MSITE-669:

    Attachment: nazgul_tools_reactor_structure.png

Structure of desired staged site.

White pom-type reactor projects only define modules and sites. Such projects do not produce
anything worth deploying - other than their part within the site:stage.

Yellow jar/bundle-type projects define a single deployable artifact, as well as documentation
in the form of a maven site. These project artifacts would be deployed to a repo in a normal
manner as well as part of a compound/staged site.
> site:stage creates incorrect structure when module paths contains sets of "../"
> -------------------------------------------------------------------------------
>                 Key: MSITE-669
>                 URL:
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: multi module, relative links, site:stage(-deploy)
>    Affects Versions: 3.1, 3.2
>            Reporter: Lennart Jörelid
>            Assignee: Lukas Theussl
>         Attachments: nazgul_tools_reactor_structure.png,
> Given the module definitions given below, the site:stage goal produces sets of maps relative
to the staging directory - i.e. outside of the target directory.
> {code:xml} 
> <modules>
>   <module>../../validation/validation-api</module>
>   <module>../../validation/validation-aspect</module>
>   <module>../parent</module>
> </modules>
> {code}
> The staged site should be fully included within the staging directory. It would appear
that relativization of links for site:stage should take special links into consideration.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message