jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2 & 3
  • MNG-2470

uniqueVersion not inherited in child projects

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0.4
  • Fix Version/s: None
  • Component/s: Inheritance and Interpolation
  • Labels:
    None
  • Environment:
    Linux
  • Complexity:
    Intermediate

Description

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.

Issue Links

is superceded by

Bug - A problem which impairs or prevents the functions of the product. MNG-3885 Modules of Maven projects are deployed with Timestamp during reactor build when uniqueVersion is set to false in parent profile

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
korebantic added a comment - 30/Jul/06 9:12 AM

same issue as discussed here: http://jira.codehaus.org/browse/MNG-1094

Show
korebantic added a comment - 30/Jul/06 9:12 AM same issue as discussed here: http://jira.codehaus.org/browse/MNG-1094
Hide
Permalink
Brett Porter added a comment - 30/Jul/06 9:12 PM

while it is discussed in MNG-1094, that looks to be for the main repository element and not the snapshot repository element

Show
Brett Porter added a comment - 30/Jul/06 9:12 PM while it is discussed in MNG-1094, that looks to be for the main repository element and not the snapshot repository element
Hide
Permalink
Max Bowsher added a comment - 12/Apr/07 4:38 PM

Works fine for me with Maven 2.0.4, 2.0.5, 2.0.6.

korebantic: Can you re-test and check you can reproduce this?

Show
Max Bowsher added a comment - 12/Apr/07 4:38 PM Works fine for me with Maven 2.0.4, 2.0.5, 2.0.6. korebantic: Can you re-test and check you can reproduce this?
Hide
Permalink
Matthew McCullough added a comment - 17/Jul/07 7:51 PM - edited

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

Show
Matthew McCullough added a comment - 17/Jul/07 7:51 PM - edited 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

People

  • Assignee:
    Brett Porter
    Reporter:
    korebantic
Vote (0)
Watch (2)

Dates

  • Created:
    30/Jul/06 9:10 AM
    Updated:
    24/Jan/09 11:52 AM
    Resolved:
    18/Dec/08 6:54 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.