Re: Site staging strategy
It appears that the attachments got snipped somewhere, so making the images available via normal browsing: *Problem:* I essentially want to know how to inject a site stage structure parser in doxia for use with maven-site-plugin, since the maven-site-plugin's usage of Doxia for running site:stage seems to assume that there is a 1:1 relation between pom parents and modules. I struggle to find a simple way to instruct the maven-site-plugin how to structure its stage site when a project has defined another parent pom than the project which included it in the build reactor. In the images below, this is the case for X-Y-api and the other projects dyed slightly yellow. *Image legend*: In the images below, solid lines indicate the reactor/module dependencies, and dotted line arrows indicate parent relations between poms. Reactor structure, and parent inheritance: http://www.jguru.se/apache/maven/site/reactor_and_inheritance.png Desired site structure: http://www.jguru.se/apache/maven/site/desired_stage_site.png 2012/12/7 Anders Hammar and...@hammar.net Lennart, Your attachments are missing. /Anders On Thu, Dec 6, 2012 at 11:49 PM, Lennart Jörelid lennart.jore...@gmail.comwrote: Hello all, I have a few reactors where two separate parent poms exist; one parent is used exclusively for reactor projects [with packagingpom/packaging] and the other parent is exclusively used for all other projects [with packaging... something not pom .../packaging]. The build itself works as expected - but the *mvn site:stage* builds a structure connecting only the irrelevant parts (i.e. the reactor poms having module definitions); the relevant projects (i.e the non-reactor projects) are left out of the staged site, and site navigation does not work in the staged site. After a tad of looking around in Doxia, I am not quite certain what should be customized to handle the difference in preferred site stage structure. There is likely a simple solution for how to retieve a staged site with desired/relevant content, but I have not found it. Could you direct me here? An example reactor structure is illustrated/attached in the image reactor_and_inheritance.png, where solid lines indicate the reactor/module dependencies, and dotted line arrows indicate parent relations between poms. Also attaching the desired site stage structure. -- +==+ | Bästa hälsningar, | [sw. Best regards] | | Lennart Jörelid +==+ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- -- +==+ | Bästa hälsningar, | [sw. Best regards] | | Lennart Jörelid | EAI Architect Integrator | | jGuru Europe AB | Mölnlycke - Kista | | Email: l...@jguru.se | URL: www.jguru.se | Phone | (skype):jgurueurope | (intl): +46 708 507 603 | (domestic): 0708 - 507 603 +==+
Site staging strategy
Hello all, I have a few reactors where two separate parent poms exist; one parent is used exclusively for reactor projects [with packagingpom/packaging] and the other parent is exclusively used for all other projects [with packaging... something not pom .../packaging]. The build itself works as expected - but the *mvn site:stage* builds a structure connecting only the irrelevant parts (i.e. the reactor poms having module definitions); the relevant projects (i.e the non-reactor projects) are left out of the staged site, and site navigation does not work in the staged site. After a tad of looking around in Doxia, I am not quite certain what should be customized to handle the difference in preferred site stage structure. There is likely a simple solution for how to retieve a staged site with desired/relevant content, but I have not found it. Could you direct me here? An example reactor structure is illustrated/attached in the image reactor_and_inheritance.png, where solid lines indicate the reactor/module dependencies, and dotted line arrows indicate parent relations between poms. Also attaching the desired site stage structure. -- +==+ | Bästa hälsningar, | [sw. Best regards] | | Lennart Jörelid +==+ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Site staging strategy
Lennart, Your attachments are missing. /Anders On Thu, Dec 6, 2012 at 11:49 PM, Lennart Jörelid lennart.jore...@gmail.comwrote: Hello all, I have a few reactors where two separate parent poms exist; one parent is used exclusively for reactor projects [with packagingpom/packaging] and the other parent is exclusively used for all other projects [with packaging... something not pom .../packaging]. The build itself works as expected - but the *mvn site:stage* builds a structure connecting only the irrelevant parts (i.e. the reactor poms having module definitions); the relevant projects (i.e the non-reactor projects) are left out of the staged site, and site navigation does not work in the staged site. After a tad of looking around in Doxia, I am not quite certain what should be customized to handle the difference in preferred site stage structure. There is likely a simple solution for how to retieve a staged site with desired/relevant content, but I have not found it. Could you direct me here? An example reactor structure is illustrated/attached in the image reactor_and_inheritance.png, where solid lines indicate the reactor/module dependencies, and dotted line arrows indicate parent relations between poms. Also attaching the desired site stage structure. -- +==+ | Bästa hälsningar, | [sw. Best regards] | | Lennart Jörelid +==+ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
