maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lennart Jörelid (JIRA) <j...@codehaus.org>
Subject [jira] (MSITE-669) site:stage creates incorrect structure when module paths contains sets of "../"
Date Mon, 17 Dec 2012 10:59:13 GMT

    [ https://jira.codehaus.org/browse/MSITE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315826#comment-315826
] 

Lennart Jörelid commented on MSITE-669:
---------------------------------------

While the sample project is created only to illustrate the symptoms for this issue, there
are several quite legitimate reasons to not wanting the reactor pom be the logical parent
for the distribution. (Separate parent poms for reactor poms not intended to be deployed/distributed
and all other artifacts intended to be deployed, for instance).

However, I suggest that we update the documentation for the maven-site-plugin, to clarify
that the {{site:stage}} goal assumes 3 things to work properly:

# The pom.xml of the topmost project in a multi-module build must define the distributionManagement
URL element (called "rootURL" hereafter). The rootURL must be the *topmost* distributionManagement
URL in the multi-module project, implying that any distributionManagement URL defined within
another project in a multimodule build must start with the rootURL and append unique paths
(to be situated "below" the rootURL).
# All projects in multi-module builds must define unique distributionManagement url elements,
below/under the root distributionManagement URL in terms of URL path.
# If the artifactId and module name (i.e. directory name) are not identical for any project
within a multi-module build, the distributionManagement URL element must be defined in the
pom.xml file in the project.

I would suggest adding these facts to the maven-site-plugin documentation, as well as a small
example holding a multimodule project containing at least one occurrence of a project where
artifactId and module name are not identical.
                
> site:stage creates incorrect structure when module paths contains sets of "../"
> -------------------------------------------------------------------------------
>
>                 Key: MSITE-669
>                 URL: https://jira.codehaus.org/browse/MSITE-669
>             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: sample.zip
>
>
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message