[ http://jira.codehaus.org/browse/MNG-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102538 ]
Matthew McCullough edited comment on MNG-2470 at 7/17/07 8:05 PM: ------------------------------------------------------------------ Similar to my issue MDEPLOY-57 where uniqueVersion is not honored in a profile at all for any directory tree multiproject usages, though the effective-pom in my case shows the right >false< value was: Similar to my issue where uniqueVersion is not honored in a profile at all > uniqueVersion not inherited in child projects > --------------------------------------------- > > Key: MNG-2470 > URL: http://jira.codehaus.org/browse/MNG-2470 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation > Affects Versions: 2.0.4 > Environment: Linux > Reporter: korebantic > Fix For: Reviewed Pending Version Assignment > > > My parent project defines the following: > <distributionManagement> > <snapshotRepository> > <id>Yo</id> > <name>Yo Repository</name> > <url>scp://yo/home/maven/www</url> > <uniqueVersion>false</uniqueVersion> > </snapshotRepository> > </distributionManagement> > When I run the following command in the child project: > mvn help:effective-pom > I get the following results: > ... > <distributionManagement> > <snapshotRepository> > <id>Yo</id> > <name>Yo Repository</name> > <url>scp://yo/home/maven/www</url> > </snapshotRepository> > </distributionManagement> > ... > It looks like inheritence is ignoring the <uniqueVersion> element. > This is also verified, when I run "mvn deploy" -- the parent project installs > a non-timestamped version in the remote repository, but the child project > installs a timestamped version. -- 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