[
http://jira.codehaus.org/browse/MRM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97696
]
Joakim Erdfelt commented on MRM-406:
------------------------------------
Try it yourself.
# Change from archiva.version to project.version
# When in trunk build the entire archiva - [trunk]$ mvn clean install
# Make a change to archiva-database.
#* This is key piece of showing this failure.
#* The change should be obvious, to show that archiva-database functionality
has been updated.
# Now build just database - [trunk/archiva-database]$ mvn clean install
# Now execute the webapp - [trunk/archiva-web/archiva-webapp]$ mvn clean
jetty:run
At this point you'll either get build failures, or when executing the webapp,
you are *NOT* using the latest archiva-database.
What happens.
# The install process changes the SNAPSHOT in the pom to a TIMESTAMP(a).
# The installing everything works, as the TIMESTAMP(a)s are all the same.
# Installing the archiva-database project causes a new TIMESTAMP(b) to be
created for it.
# Running the archiva-webapp, uses the parent-pom reference as SNAPSHOT, which
resolves to TIMESTAMP(a), and as such, the archiva-database it uses is the old
TIMESTAMP(a) version, not the intended TIMESTAMP(b) version.
This is a *well known* issue with maven.
We've hit this with redback too. It uses the same technique. I can't speak
for continuum.
I contend that this is *not* and issue with archiva, but an issue with the
maven-release-plugin, for not performing the updates to the versions correctly.
Solution:
# Fix the maven-release-plugin to do version updates correctly.
> 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
