Checking Maven Version Update Passes

Question

When I try to use versions:use-releases , my release repository is marked as “disabled”, which means that snapshot dependencies are not allowed for release. I do not understand why the repository is considered to be disabled.

Here is the abbreviated debug output from the assembly:

 [DEBUG] (f) remoteArtifactRepositories = [ id: snapshots url: http://maven.live.hostname.net/content/repositories/snapshots/ layout: default snapshots: [enabled => true, update => daily] releases: [enabled => true, update => daily] , id: company-nexus url: http://maven.live.hostname.net/content/groups/public/ layout: default snapshots: [enabled => false, update => daily] releases: [enabled => true, update => daily] ] [...] [DEBUG] Looking for a release of promotion-test-central:promotion-test-central:jar:1.6.0-SNAPSHOT [INFO] artifact promotion-test-central:promotion-test-central: checking for updates from snapshots [DEBUG] Reading resolution-state from: /home/tester/.m2/repository/promotion-test-central/promotion-test-central/resolver-status.properties [DEBUG] Writing resolution-state to: /home/tester/.m2/repository/promotion-test-central/promotion-test-central/resolver-status.properties [DEBUG] Skipping update check for artifact promotion-test-central:promotion-test-central (/home/tester/.m2/repository/promotion-test-central/promotion-test-central/maven-metadata-company-nexus.xml) from disabled repository company-nexus (http://hostname/content/groups/public/) 

I run a setup that requests central to our Nexus instance, and also sets up a global snapshot repository:

  <mirrors> <mirror> <id>mendeley-nexus</id> <mirrorOf>central</mirrorOf> <url>http://maven.live.chonp.net/content/groups/public/</url> </mirror> </mirrors> <profiles> <profile> <id>default</id> <repositories> <repository> <id>snapshots</id> <url>http://maven.live.chonp.net/content/repositories/snapshots/</url> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> </profile> </profiles> <activeProfiles> <activeProfile>default</activeProfile> </activeProfiles> 

There is a release version and a snapshot of the dependency in question, and the repository works exactly as expected in all other respects.

Answer 1

Your settings.xml file must be configured as described in the Nexus book . Your configuration will not work, as it only partially cancels the Maven supermag.

Answer 2

I also came across this. I was able to get past this:

  <repository> <id>my-snapshots</id> <url>https://nexus.corp.company.com/nexus/content/repositories/snapshots</url> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>true</enabled> </releases> </repository> 

which was a deviation from the previous one:

  <releases> <enabled>false</enabled> </releases> 

This happens when Maven looks at the metadata for your current artifact and restricts its search to only repositions that may also contain this artifact.