[ http://jira.codehaus.org/browse/MRM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97852 ]
Brett Porter commented on MRM-406: ---------------------------------- good idea. Let the release plugin take care of updating it. actually, even if we just populate the versions in dependency management instead of using ${project.version}, it should work - the release plugin does deal correctly with depMgmt. > Replace the archiva.version propertry with project.version > ---------------------------------------------------------- > > Key: MRM-406 > URL: http://jira.codehaus.org/browse/MRM-406 > Project: Archiva > Issue Type: Improvement > Affects Versions: 1.0-alpha-1 > Reporter: Franz Allan Valencia See > Assignee: Joakim Erdfelt > Fix For: 1.0-alpha-1 > > Attachments: MRM-406-archiva-parent.patch > > > There is no need for the archiva.version property in the pom because this can > be represented by the project.version property. Furthermore this can cause > problems when doing a release with continuum. -- 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