Check the effective pom to see what Maven is working on. This will show what repositories are enabled and how configured.
mvn help:effective-pom -P theprofileyoursusing But, I seriously wonder why you would like to use a snapshot repo when doing a release. A release should never use snapshots. /Anders On Mon, May 23, 2011 at 10:15, Jérémy <[email protected]> wrote: > Hi, > > I noticed a weird behavior with the versions resolution of Maven 3.0.3. > Here's my setup: I use Nexus and have a first repository group containing > release and snapshots versions and a second repository group with only > snapshots. > When I want to release a product, I want to pick only the release versions > of the first repository group and snapshots versions of the second > repository group. > In my settings.xml, I have a profile with the following configurations: > <repositories> > <repository> > <id>public</id> > <url>http://artifacts/content/groups/public</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>false</enabled> > </snapshots> > </repository> > <repository> > <id>allowed-snapshots</id> > <url>http://artifacts/content/groups/allowed-snapshots/</url> > <snapshots> > <enabled>true</enabled> > </snapshots> > </repository> > </repositories> > With this configuration, Maven picks up snapshots from the public > repository. However if I remove the second repository, the resolution works > as attended. It seems that the enabled variable acts as a global variable > across settings.xml. Is that a bug? > > Cheers, > Jérémy >
