[jira] [Closed] (MSITE-671) Regression: site:stage no longer functions for MM projects.

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MSITE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MSITE-671.
--------------------------------
    Fix Version/s:     (was: waiting-for-feedback)
       Resolution: Incomplete

No feedback received.

> Regression: site:stage no longer functions for MM projects.
> -----------------------------------------------------------
>
>                 Key: MSITE-671
>                 URL: https://issues.apache.org/jira/browse/MSITE-671
>             Project: Maven Site Plugin
>          Issue Type: Bug
>          Components: site:stage(-deploy)
>    Affects Versions: 3.2
>         Environment: Debian Linux OpenJDK 7 mvn 3.0.4
>            Reporter: Fred Cooke
>            Priority: Major
>
> With site 3.0 I could run mvn site:site site:stage from the top of my multi-module project, and it would accumulate a working site in my chosen directory exactly as per the instructions here:
> https://maven.apache.org/plugins/maven-site-plugin/stage-mojo.html
> "Deploys the generated site to a local staging or mock directory based on the site URL specified in the {{<distributionManagement>}} section of the POM.  It can be used to test that links between module sites in a multi-module build works."
> I didn't try 3.1, but with 3.2 the links from the parent site to the children did not function. I didn't investigate further, though I could if required.
> More info, this is what I have in my parent/aggregator:
> {code:xml}
> 		<site>
> 			<!-- Use mvn site:stage to get a working local copy of site AFTER building it normally -->
> 			<id>local-viewing</id>
> 			<url>${project.baseDir}/target/staging/</url>
> 		</site>
> {code}
> It was suggested (by Robert) that it may work with this variable used instead: ${project.executionProject.basedir} however the staging directory is only relevant at the top level anyway, so I don't see why that should be necessary. Again, I didn't try it, but can if this is considered intentional behaviour change, as opposed to a regression.
> These issues may (or may not) be related:
> http://jira.codehaus.org/browse/MSITE-600
> http://jira.codehaus.org/browse/MSITE-602
> http://jira.codehaus.org/browse/MSITE-649



--
This message was sent by Atlassian Jira
(v8.20.10#820010)