All, While many of you may not be using Nexus, I thought I would throw out the question here see if someone could point me in the right direction.
We are currently using Nexus [1] as a Maven repository to hold the revision of rave trunk we want to use as snapshot version. Since we want some of the features from the current snapshot, but not all, we deploy the version we want to nexus to try and avoid getting the most up to date changes from rave trunk. This works when I deploy to nexus, more recently than a commit to rave trunk. So for example if I push the version I want to nexus, I can mvn clean install my project over and over always getting the correct code. Once there is a push to rave trunk, it seems to start pulling in the latest snapshot changes causing errors in my project. It looks like it is pulling down both from our nexus server and apache snapshot maven repo but then using the latest version. What I want is to always use our nexus repo no matter what. What I noticed in my .m2 folder is any component of rave which is pulling down snapshot has the following file located inside: resolver-status.properties Its contents are as follows: #NOTE: This is an internal implementation file, its format can be changed without prior notice. #Wed Aug 07 11:53:24 EDT 2013 maven-metadata-apache.snapshots.xml.lastUpdated=1375873005173 maven-metadata-EclipseLink.xml.lastUpdated=1375873004611 maven-metadata-EclipseLink.xml.error= maven-metadata-nexus-snapshots.xml.lastUpdated=1375890804831 What I assume is happening is if apache snapshots have been updated most recently it is using those files. This cannot be coming from the build of our own project, because we completely stripped out the apache snapshots repository, but rather, my guess, when base rave is building. Would anyone know if there is a way to stop getting the latest snapshot from apaches maven repo and only look at our nexus repo? Thanks in advance, Dan Gornstein [1] http://www.sonatype.org/nexus/
