Or not :(

Here is the case layout:
nuxeo-distribution/
|-- nuxeo-distribution-jboss/
|-- ...

Running from root module (nuxeo-distribution), default classifier of a sub-module is deployed with a unique version: Uploading: http://maven.in.nuxeo.com/snapshots/org/nuxeo/ecm/distribution/nuxeo-distribution-jboss/5.3.1-SNAPSHOT/nuxeo-distribution-jboss-5.3.1-20091102.184222-97-nuxeo-dm.zip whereas deployed from the sub-module (nuxeo-distribution-jboss), it is deployed without unique version: Uploading: http://maven.in.nuxeo.com/snapshots/org/nuxeo/ecm/distribution/nuxeo-distribution-jboss/5.3.1-SNAPSHOT/nuxeo-distribution-jboss-5.3.1-SNAPSHOT-nuxeo-dm.zip

Running "mvn help:effective-pom" gives the same result (uniqueVersion=false) from both modules (parent and child):
   (...)
   <profile>
     <id>qa</id>
     <distributionManagement>
       <snapshotRepository>
         <uniqueVersion>false</uniqueVersion>
         <id>snapshots</id>
         <url>http://maven.in.nuxeo.com/snapshots</url>
       </snapshotRepository>
     </distributionManagement>
   </profile>
 </profiles>
 <distributionManagement>
   <snapshotRepository>
     <id>nuxeo-snapshot</id>
<url>http://maven.nuxeo.org/nexus/content/repositories/nuxeo-snapshot</url>
     <uniqueVersion>false</uniqueVersion>
   </snapshotRepository>
 </distributionManagement>

The parent POM of nuxeo-distribution also has a distributionManagement but without uniqueVersion option as I prefer to keep this behavior where it isn't needed. I also had to set this configuration in a profile (qa) which is used to deploy in an internal repository.

Is it a known issue that in some case, this parameter is not taken in account ? Or is it a profile bug ?

Thanks,


Julien CARSIQUE a écrit :
Fixed with <uniqueVersion>false</uniqueVersion> in distributionManagement tag. I hope we won't have new issues because of this (non updated artifacts, ...).

Thanks

Julien CARSIQUE a écrit :
Hello,

We encounter a new issue with snapshots resolution on Maven 2.0.10 (for now, we cannot migrate to 2.1 or 2.2)

Some of our modules may generate various builds depending on the active profiles. We distinguish those builds with classifiers but those various builds are not (and cannot) be generated during the same maven execution. Resolving the snapshot and looking for the wanted artifact, Maven looks for an artifact with the wanted artifact and classifier but with the snapshot keyword resolution based on the last updated metadata, corresponding to one classifier only.

Here is a sample case:
- we deploy org.nuxeo.ecm.distribution:nuxeo-distribution-jboss:5.3.1-SNAPSHOT:nuxeo-ep:zip => org/nuxeo/ecm/distribution/nuxeo-distribution-jboss/5.3.1-SNAPSHOT/nuxeo-distribution-jboss-5.3.1-20091029.115623-10.pom => org/nuxeo/ecm/distribution/nuxeo-distribution-jboss/5.3.1-SNAPSHOT/nuxeo-distribution-jboss-5.3.1-20091029.115623-10-nuxeo-ep.zip

- then we deploy org.nuxeo.ecm.distribution:nuxeo-distribution-jboss:5.3.1-SNAPSHOT:nuxeo-dm:zip => org/nuxeo/ecm/distribution/nuxeo-distribution-jboss/5.3.1-SNAPSHOT/nuxeo-distribution-jboss-5.3.1-20091029.122446-11.pom => org/nuxeo/ecm/distribution/nuxeo-distribution-jboss/5.3.1-SNAPSHOT/nuxeo-distribution-jboss-5.3.1-20091029.122446-11-nuxeo-dm.zip

- org/nuxeo/ecm/distribution/nuxeo-distribution-jboss/5.3.1-SNAPSHOT/maven-metadata.xml contains:
<metadata>
<groupId>org.nuxeo.ecm.distribution</groupId>
<artifactId>nuxeo-distribution-jboss</artifactId>
<version>5.3.1-SNAPSHOT</version>
<versioning>
  <snapshot>
    <timestamp>20091029.122446</timestamp>
    <buildNumber>11</buildNumber>
  </snapshot>
  <lastUpdated>20091029122932</lastUpdated>
</versioning>
</metadata>

Trying to build a project depending on nuxeo-ep classifier, we get the following issue: Downloading: .../org/nuxeo/ecm/distribution/nuxeo-distribution-jboss/5.3.1-SNAPSHOT/nuxeo-distribution-jboss-5.3.1-20091029.122446-11-nuxeo-ep.zip
  [ERROR] BUILD ERROR
  [INFO] Failed to resolve artifact.
  Missing:
  ----------
1) org.nuxeo.ecm.distribution:nuxeo-distribution-jboss:zip:nuxeo-ep:5.3.1-SNAPSHOT


Do you know this issue ? Is it fixed in new versions ? Do you have a work around ?

Best regards,
Julien



--
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]

Reply via email to