Hi, we just migrated from Artifactory 2.0.1 to 2.2.5 by exporting and importing the whole system and we are having a problem when resolving snapshot version of plugins. It is noteworthy that this phenomena is not present when using Artifactory 2.0.1. Next i will describe the issue using maven-archetype-plugin but it also happen with other plugins such as maven-pmd-plugin. Maven complains about plugin metadata in the following way: ----ERROR BEGIN ----- Project ID: org.apache.maven.plugins:maven-archetype-plugin
Reason: Error getting POM for 'org.apache.maven.plugins:maven-archetype-plugin' from the repository: Failed to resolve artifact, possibly due to a repository list that is not appropriately equipped for this artifact's metadata. org.apache.maven.plugins:maven-archetype-plugin:pom:2.0-alpha-6-SNAPSHOT from the specified remote repositories: local.artifactory (http://tstlnxrepo.datacenter:8180/artifactory/repos/) for project org.apache.maven.plugins:maven-archetype-plugin ----ERROR END----- Up to this point Plugin metadata was well resolved and maven-metadata.xml for maven-archetype-plugin was also well resolved due to the version 2.0-alpha-6-SNAPSHOT was selected. When quering plugin metadata next is retrived: resource queried: org/apache/maven/plugins/maven-archetype-plugin/maven-metadata.xml ---- maven-metadata.xml BEGIN----- <?xml version="1.0" encoding="UTF-8"?> <metadata> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-archetype-plugin</artifactId> <versioning> <latest>2.0-alpha-6-SNAPSHOT</latest> <release>2.0</release> <versions> <version>1.0-alpha-3</version> <version>1.0-alpha-4</version> <version>1.0-alpha-7</version> <version>2.0-alpha-1</version> <version>2.0-alpha-2</version> <version>2.0-alpha-3</version> <version>2.0-alpha-4</version> <version>2.0-alpha-5</version> <version>2.0</version> <version>2.1-SNAPSHOT</version> <version>2.0-SNAPSHOT</version> <version>2.0-alpha-5-SNAPSHOT</version> <version>2.0-alpha-6-SNAPSHOT</version> </versions> <lastUpdated>20101204150725</lastUpdated> </versioning> </metadata> ---- maven-metadata.xml END----- Note that latest version is 2.0-alpha-6-SNAPSHOT (actually used). The final step, where maven fails, correspond on detecting the snapshot version to be used. To do that, maven queries for maven-metadata.xm file where the version to be used is registered. queried resource: org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-6-SNAPSHOT/maven-metadata.xm ---- maven-metadata.xm BEGIN----- <?xml version="1.0" encoding="UTF-8"?> <metadata> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-archetype-plugin</artifactId> <version>2.0-alpha-6-SNAPSHOT</version> <versioning> <snapshot> <timestamp>20100912.215611</timestamp> <buildNumber>2</buildNumber> </snapshot> <lastUpdated>20100912215836</lastUpdated> </versioning> </metadata> ---- maven-metadata.xm END----- The most interesting thing is that mavens complains but the maven archetype plugin for the registered version is present in the repository. Next available resources are listed: org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-6-SNAPSHOT/maven-archetype-plugin-2.0-alpha-6-20100912.215611-2.jar org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-6-SNAPSHOT/maven-archetype-plugin-2.0-alpha-6-20100912.215611-2.pom Thanks in advance. -- Mario Matias Urbita [email protected] www.fluxit.com.ar Calle 9 #865 La Plata / Buenos Aires / Argentina +54 221 4831722 Int:308 ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
