maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Henkel (JIRA)" <j...@codehaus.org>
Subject [jira] (MSITE-634) Invalid links to sub-modules when specifying site url using a profile
Date Tue, 03 Apr 2012 06:28:03 GMT

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

Matthias Henkel commented on MSITE-634:
---------------------------------------

Thank you for your immediate response!

Unfortunately adding the URL didn't help. I added the URL <url>https://projects.company.com/application/filestore/site/siteFixing/</url>
in the parent pom and <url>https://projects.company.com/application/filestore/site/siteFixing/module</url>
in the child pom - as "root element", not in <distributionManagement>/<site>/<url>.

These are exactly the links to the location where the deployed site is available but the generated
relative link didn't change at all. (Of course "company" and "application" are only replacements
for the real values I use.)
Am I missing something? I still wonder why everything works fine when using 2.2 or not using
a profile.
                
> Invalid links to sub-modules when specifying site url using a profile
> ---------------------------------------------------------------------
>
>                 Key: MSITE-634
>                 URL: https://jira.codehaus.org/browse/MSITE-634
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: multi module, relative links
>    Affects Versions: 2.3
>            Reporter: Matthias Henkel
>         Attachments: childpom.xml
>
>
> When using a profile for specifying the site url the links to the sub-modules get broken.
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <project xmlns="http://maven.apache.org/POM/4.0.0" 
>    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
>    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> 	<modelVersion>4.0.0</modelVersion>
> 	<groupId>com.company.application</groupId>
> 	<artifactId>application</artifactId>
> 	<packaging>pom</packaging>
> 	<version>04.00.02-9_19-SNAPSHOT</version>
> 	<name>application</name>
> 	<prerequisites>
> 		<maven>2.2.1</maven>
> 	</prerequisites>
> 	<build>
> 		<pluginManagement>
> 			<plugins>
> 				<plugin>
> 					<groupId>org.apache.maven.plugins</groupId>
> 					<artifactId>maven-site-plugin</artifactId>
> 					<version>2.3</version>
> 				</plugin>
> 			</plugins>
> 		</pluginManagement>
> 	</build>
> 	<profiles>
> 		<profile>
> 			<id>company</id>
> 			<distributionManagement>
> 				<site>
> 					<id>application.site</id>
> 					<url>scpexe://projects.company.com/srv/filestore/application/site/siteFixing/</url>
> 				</site>
> 			</distributionManagement>
> 		</profile>
> 	</profiles>
> 	<modules>
> 		<module>com.company.application.module</module>
> 	</modules>
> </project>
> {code}
> Executed command: {{mvn clean site-deploy -P company}}
> Reproducible with: {{maven-site-plugin}} {{2.3}} but not with {{2.2}}.
> When specifying the {{distributionManagement}} section outside of a profile everything
works fine.
> The site of the parent module is deployed to https://projects.company.com/application/filestore/site/siteFixing/index.html
but the link to the sub-module points to https://projects.company.com/module/index.html even
though the sub-module has been deployed to https://projects.company.com/application/filestore/site/siteFixing/module/index.html
.

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