Hi Kenny, Kenney Westerhof wrote on Saturday, May 06, 2006 3:06 PM:
> On Sat, 6 May 2006, Brett Porter wrote: > > Isn't this behaviour the default anyway? Appending the module's > artifactId to the parent's url? At least for the scm tags this is wrong. These tags must be expanded with the current folder name. Otherwise you require the folder named as the artifactID. This is not reasonable for bigger projects, e.g.: project + core ++ providers +++ common Here "common" contains a jar artifact with classes common for all "providers" in the project's core functionality. The path identifies the artifact uniquely. Unfortunately you cannot simply call your artifact "common" nor "project_common" nor "core_common", but you have to think of a unique artifactId that allows the artifact to get packed into a flat lib directory as used by web apps or ears. But now I have to overwrite in every pom the scm definitions, since the default breaks the URLs although Maven should have know better from the path in use. Same goes for project url or the site url in the distributionsManagement, because something like (assuming a super POM in each parent level): http:///docbase/project_super_pom/core_super_pom/providers_super_pom/project_core_providers_common is quite silly compared to: http:///docbase/project/core/providers/common So there should be some possibility to influence the URL expansions in multi module mode. > > -- Kenney > >> I think this would be a worthwhile addition to JIRA. I'm not sure if >> it's already in there. I know it was pointed out as an issue a while >> ago and we were going to look at changing the behaviour from >> automatic append to controlled appending by expressions like you've >> highlighted in a future version of the POM. >> >> Would you mind filing it? Where? "MNG", component "Inheritance & interpolation" ? - Jörg >> >> - Brett >> >> On 5/6/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: >>> I think there needs to be some additional POM elements that allows a >>> parent POM to provide defaults to a child POM that are different >>> from the values used by the parent POM itself. >>> >>> Here's an example: >>> >>> In my parent POM, I want to say >>> >>> <url>http://tapestry.apache.org/tapestry5/</url> >>> >>> But I want all my child modules to use the URL: >>> >>> <url>http://tapestry.apache.org/tapestry5/${pom.artifactId}</url> >>> >>> >>> I could see this expressed, in my parent pom, as something like: >>> >>> <project> ... >>> <url>http://tapestry.apache.org/tapestry5/</url> >>> >>> ... >>> >>> <childDefaults> >>> > <url>http://tapestry.apache.org/tapestry5/${pom.artifactId}</url> >>> </childDefaults> >>> >>> ... >>> -- >>> Howard M. Lewis Ship >>> Independent J2EE / Open-Source Java Consultant >>> Creator and PMC Chair, Apache Tapestry >>> Creator, Jakarta HiveMind >>> >>> Professional Tapestry training, mentoring, support >>> and project work. http://howardlewisship.com >>> >>> > --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> > --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
