You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Fred Cooke (JIRA)" <ji...@codehaus.org> on 2012/12/31 15:37:13 UTC

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

Fred Cooke created MSITE-671:
--------------------------------

             Summary: Regression: site:stage no longer functions for MM projects.
                 Key: MSITE-671
                 URL: https://jira.codehaus.org/browse/MSITE-671
             Project: Maven 2.x and 3.x 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


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 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

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

Posted by "Fred Cooke (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MSITE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316454#comment-316454 ] 

Fred Cooke commented on MSITE-671:
----------------------------------

OK, I did some further playing and my results are as follows:

3.0 just works, with baseDir or basedir, equally.

3.1 and 3.2 behave identically (for my purposes) in that they first report the correct path, and then fail, with both baseDir and basedir, but differently. baseDir is not expanded, however basedir is expanded, to an absolute path, and then complains that it's not an absolute path when it actually IS! I hope this helps track it down.

Also, my original report, done from memory (like Swiss cheese!) is wrong, links weren't broken, build was.

{noformat}
3.0 baseDir

[INFO] --- maven-site-plugin:3.0:stage (default-cli) @ reporting-parent ---
[INFO] Using this base directory for staging: /home/fred/workspace/tara/target/staging/

works

3.0 basedir

[INFO] --- maven-site-plugin:3.0:stage (default-cli) @ reporting-parent ---
[INFO] Using this base directory for staging: /home/fred/workspace/tara/target/staging/

works

3.1 baseDir

[INFO] --- maven-site-plugin:3.1:stage (default-cli) @ reporting-application ---
[INFO] Using this base directory for staging: /home/fred/workspace/tara/target/staging/
<snip>
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.1:stage (default-cli) on project reporting-application: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.1:stage failed: Base URI is not absolute: $%7bproject.baseDir%7d/target/staging/ -> [Help 1]

3.1 basedir

[INFO] --- maven-site-plugin:3.1:stage (default-cli) @ reporting-application ---
[INFO] Using this base directory for staging: /home/fred/workspace/tara/target/staging/
<snip>
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.1:stage (default-cli) on project reporting-application: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.1:stage failed: Base URI is not absolute: /home/fred/workspace/tara/target/staging/ -> [Help 1]

3.2 baseDir

[INFO] --- maven-site-plugin:3.2:stage (default-cli) @ reporting-application ---
[INFO] Using this base directory for staging: /home/fred/workspace/tara/target/staging/
<snip>
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.2:stage (default-cli) on project reporting-application: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.2:stage failed: Base URI is not absolute: $%7bproject.baseDir%7d/target/staging/ -> [Help 1]

3.2 basedir

[INFO] --- maven-site-plugin:3.2:stage (default-cli) @ reporting-application ---
[INFO] Using this base directory for staging: /home/fred/workspace/tara/target/staging/
<snip>
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.2:stage (default-cli) on project reporting-application: Execution default-cli of goal org.apache.maven.plugins:maven-site-plugin:3.2:stage failed: Base URI is not absolute: /home/fred/workspace/tara/target/staging/ -> [Help 1]
{noformat}

                
> Regression: site:stage no longer functions for MM projects.
> -----------------------------------------------------------
>
>                 Key: MSITE-671
>                 URL: https://jira.codehaus.org/browse/MSITE-671
>             Project: Maven 2.x and 3.x 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
>
> 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 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