Return-Path: Delivered-To: apmail-maven-issues-archive@minotaur.apache.org Received: (qmail 59276 invoked from network); 2 May 2009 07:50:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 May 2009 07:50:14 -0000 Received: (qmail 32370 invoked by uid 500); 2 May 2009 07:50:14 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 32267 invoked by uid 500); 2 May 2009 07:50:13 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 32257 invoked by uid 99); 2 May 2009 07:50:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 May 2009 07:50:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [63.246.2.115] (HELO codehaus01.managed.contegix.com) (63.246.2.115) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 May 2009 07:50:06 +0000 Received: from codehaus01.managed.contegix.com (localhost.localdomain [127.0.0.1]) by codehaus01.managed.contegix.com (Postfix) with ESMTP id 08C4C14A81A1 for ; Sat, 2 May 2009 02:49:45 -0500 (CDT) Message-ID: <3862032.109781241250585002.JavaMail.haus-jira@codehaus01.managed.contegix.com> Date: Sat, 2 May 2009 02:49:45 -0500 (CDT) From: "Paul Harrison (JIRA)" To: issues@maven.apache.org Subject: [jira] Commented: (MNG-2915) No way to avoid adding artifactId to site urls In-Reply-To: <134882995.1175218534252.JavaMail.haus-jira@codehaus01.managed.contegix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 4e90ceb663894a42f12c0e28abbab431 X-Virus-Checked: Checked by ClamAV on apache.org [ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174940#action_174940 ] Paul Harrison commented on MNG-2915: ------------------------------------ I would like to add a plea for this behaviour to be modified - we too have a similar 3 level pom inheritance hierarchy, and it is irritating to have to specify the URLs in the final level when the root is specified in the top level because the intermedate level is automactically inserted. I think that the problems come about here because there is not a clear distinction made between pom inhertance and project aggregation - typically if a project only inherits from another project then the values should only be inherited, without modification - it a project is an aggregated child as well, then various URLs can have artifactIds automatically added to the end. Even with this modification to behaviour I would also support the suggestion above that automatic appending of artifactId only occurs when the URL ends explictly with a "/" - this allows for more complex URL layouts to be specified in the root POM with the use of variables such as the scpexe://host/blah/${project.artifactId}/${project.version} which I think is a rather commonly desired layout. > No way to avoid adding artifactId to site urls > ---------------------------------------------- > > Key: MNG-2915 > URL: http://jira.codehaus.org/browse/MNG-2915 > Project: Maven 2 > Issue Type: Improvement > Components: Sites & Reporting > Affects Versions: 2.0.5 > Reporter: Richard van der Hoff > Priority: Minor > Fix For: 3.x > > > Currently, whenever a child pom inherits from a parent (and doesn't override the relevant settings), both project.url and project.distributionManagement.site.url have the name of the child artifact appended. > It would be nice to be able to have something like > :code: > scpexe://host/blah/${project.artifactId}/${project.version} > :code: > and have this inherited to all child poms in the obvious way. > My usecase for this is that we have a single parent pom for all our projects, with useful settings such as distributionManagement, and I'd like to be able to deploy their sites to a single directory and have Apache generate me a directory listing for all the child projects. However, I curently have no way of releasing the parent project without obliterating the list of child projects. -- 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