maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <>
Subject [jira] (MSITE-669) site:stage creates incorrect structure when module paths contains sets of "../"
Date Sun, 10 Feb 2013 08:32:13 GMT


Herve Boutemy commented on MSITE-669:

I just saw the issue and proposed fix: I need to read it more in depth, but I think this is
the good approach, ie propose an option for user-supplied root url in case automatic (too
magic?) value is not what is expected by developer (who is ever smarter than machine, or can
imagine situations not expected by plugin developers :) )

notice I didn't see any modification in site:stage-deploy goal: I suppose it will deploy in
wrong directory if stageSiteRootURL is used during staging, no?
> 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 Jorelid
>            Assignee: Lukas Theussl
>         Attachments: msite_669.patch, msite_669_v2.patch, msite_669_v3.patch, nazgul_tools_project_dependencies.png,
nazgul_tools_project_dependencies.png, 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