Hello,
I have an issue with Nexus that seems to be linked to Maven.
Getting a snapshot from a Nexus group including two repositories doesn't
give me the latest one.
Here's the metadata, I'm waiting for the latest artifact (from internal
repository) which is 5.2.1-20091006.153450-66 but I get an older one
(from public repository) 5.2.1-20090925.015004-82.
It appears to be because of the buildnumber which is inevitably
inconsistent because those artifacts may come from two different
repositories.
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<groupId>org.nuxeo</groupId>
<artifactId>nuxeo-ecm</artifactId>
<version>5.2.1-SNAPSHOT</version>
<versioning>
<snapshot>
<timestamp>20090925.015004</timestamp>
<buildNumber>*82*</buildNumber>
</snapshot>
<lastUpdated>20091006153451</lastUpdated>
</versioning>
</metadata>
Bad: nuxeo-ecm-5.2.1-20090925.015004-*82*.pom
Good: nuxeo-ecm-5.2.1-20091006.153450-*66*.pom
Here's an answer I get from Nexus mailing list:
<< this seems like a Maven issue. Nexus uses the Maven Artifact stuff
(version 2.2.1 currently), and this is from there:
http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/DefaultArtifactVersion.java?view=markup
It seems that only build number is compared at all. This would explain
why maven and also nexus behaves the same wrong way. >>
This wrong behavior breaks the continuous integration infrastructure
I've setup and I don't see how to workaround this.
Thanks for help,
--
Julien Carsique, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
