[
http://jira.codehaus.org/browse/MRM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97833
]
Joakim Erdfelt commented on MRM-406:
------------------------------------
Mulling about this for a while. I see a third solution.
* Remove all <dependencyManagement> entries for archiva related
modules/projects.
* Remove archiva.version property.
* Set <version> in all <dependencies> in all archiva modules/projects to
project.version
It's the dependencyManagement fault that we are working around with the
archiva.version property.
> 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
