maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Katsubo (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-3244) inherited site url not properly handling parameters
Date Wed, 12 Feb 2014 16:43:14 GMT

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

Dmitry Katsubo commented on MNG-3244:
-------------------------------------

I have jumped to this issue from MSITE-334, as I have the same issue with automatic appending
of {{artifactId}} to inherited site URL, which does not work well with custom "templated"
URLs.
In our environment we use URL like this:
{code}
dav:http://host/nexus/content/sites/maven-site/${project.groupId}/${project.artifactId}/${project.version}/
{code}

> inherited site url not properly handling parameters
> ---------------------------------------------------
>
>                 Key: MNG-3244
>                 URL: https://jira.codehaus.org/browse/MNG-3244
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Inheritance and Interpolation, Sites & Reporting
>    Affects Versions: 2.0.7
>            Reporter: Jacob Robertson
>            Assignee: Brian Fox
>             Fix For: Issues to be reviewed for 3.x
>
>         Attachments: fix-inherited-site-url.patch, guide-site.patch, mng-3244_patch.txt
>
>
> Here is the test case to reproduce this problem.  Take the following two pom.xml files
> {code:xml}<?xml version="1.0" encoding="UTF-8"?>
> <project>
> 	<groupId>org.bar</groupId>
> 	<artifactId>foo</artifactId>
> 	<name>foo</name>
> 	<version>1.0-SNAPSHOT</version>
> 	<packaging>pom</packaging>
> 	<modelVersion>4.0.0</modelVersion>
> 	<distributionManagement>
> 		<site>
> 			<id>foo-site</id>
> 			<url>file://C:/Documents and Settings/foo/.m2/site/${project.artifactId}</url>
> 		</site>
> 	</distributionManagement>
> </project>{code}
> {code:xml}<?xml version="1.0" encoding="UTF-8"?>
> <project>
> 	<groupId>org.bar</groupId>
> 	<artifactId>baz</artifactId>
> 	<name>baz</name>
> 	<version>1.0-SNAPSHOT</version>
> 	<packaging>pom</packaging>
> 	<modelVersion>4.0.0</modelVersion>
> 	<parent>
> 		<artifactId>foo</artifactId>
> 		<groupId>org.bar</groupId>
> 		<version>1.0-SNAPSHOT</version>
> 	</parent>
> </project>{code}
> And run the site-deploy goal on each.  What you get under the site directory is this
> {noformat}- site
> /- foo
> ---/site docs
> /- baz
> ---/- baz (extra directory)
> --- ---/site docs{noformat}
> This is the simplest test case.  In the case where I have a "grandparent" pom, the site
directory uses the grandparent/parent as the path to the site, and doesn't use the actual
artifactId of the artifact I'm creating the site for.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message