maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelly Davis (JIRA)" <>
Subject [jira] Commented: (MNG-1031) SCM connection attribute being inherited incorrectly
Date Fri, 02 Feb 2007 18:53:44 GMT


Kelly Davis commented on MNG-1031:

I am using 2.0.4 and I have run into this issue. I moved my scm stuff into the parent pom
and the module containing the pom is not a parent of the child project. It seems like there
is no way given this circumstance to have maven do the right thing as far as the expansion
on the developerConnection url. I want to leave the module blank and if I am using CVS then
it should not add the leading '/'. If I am using svn then it is ok to have the '/' and also
for, it is ok to have the '/'. Please consider re-opening
this because the solution above is very in-elegant and leads to boiler-plate in all of our
organizations poms.

> SCM connection attribute being inherited incorrectly
> ----------------------------------------------------
>                 Key: MNG-1031
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0-beta-2
>            Reporter: Matthew Beermann
> (Not sure of the correct component, but taking a stab at it...)
> It appears that the <connection> attribute of <scm> is being modified as
it is inherited, but not correctly. For example, if my parent project had something like:
> <scm>
>     <connection>scm:cvs:pserver:anonymous@server:/projects:</connection>
> </scm>
> ...then the final value of the attribute, as seen by the children and any plugins, ends
up looking something like:
>     scm:cvs:pserver:anonymous@server:/projects:/my-artifact-id
> ...which is wrong. It appended the artifact id automagically, which is good, but it added
a leading slash that CVS doesn't like at all. It does work in Subversion I suspect. Anyway,
I'm not sure where the appending happens, so reassign as needed...

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message