[
http://jira.codehaus.org/browse/MRM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97632
]
Brett Porter commented on MRM-406:
----------------------------------
Joakim - I don't think your 'each and every time' comment is correct, I can
only see this happening if you are using snapshots from the web (since it might
mistakenly use the snapshot version across the board instead of the -SNAPSHOT).
Though I've never actually seen that happen either.
Seems like a bug that should be fixed in Maven rather than using this
workaround, so I agree with the patch at this stage.
> 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
