[
http://jira.codehaus.org/browse/MNG-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155184#action_155184
]
Kenneth Flynn commented on MNG-3244:
------------------------------------
I'm fairly new to Maven, but I find the default behavior for all URLs very
confusing. I understand the desired behavior, but many projects are just not
arranged like the default behavior implies. The same URL alteration happens for
SCM urls, the overall project URL, etc. I had initially created a corporate
parent POM that I had hoped could work about 85% of our SVN repos by default,
but I will have to override every one in the actual POM for each project (the
suggested workaround).
I would strongly argue for a change to the POM to be able to turn this off
globally (not just for site URLs). I'd prefer for that to be the default (I
think the current behavior violates the principle of least surprise), but
that's water under the bridge in terms of compatibility at this point. We
really need a way of turning this off though--I really think it will lead to
simpler POMs.
> inherited site url not properly handling parameters
> ---------------------------------------------------
>
> Key: MNG-3244
> URL: http://jira.codehaus.org/browse/MNG-3244
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation, Sites & Reporting
> Affects Versions: 2.0.7
> Reporter: Jacob Robertson
> Assignee: Brian Fox
> Fix For: 3.0-alpha-3
>
> Attachments: fix-inherited-site-url.patch, guide-site.patch
>
>
> Here is the test case to reroduce this problem. Take the following two
> pom.xml files
> <?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>
> <?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>
> And run the site-deploy goal on each. What you get under the site directory
> is this
> - site
> /- foo
> ---/site docs
> /- baz
> ---/- baz (extra directory)
> --- ---/site docs
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
