Hi I have Maven2 installed on my workstation at work, and it works fine... Love it.
I talked one of our adminstrators into installing Nexus on one of our development servers to compliment our Subversion repository. As soon as we got Nexus running, I installed the 3rd party artifacts I use in my existing projects and two 3rd party plugins. I decided to test my existing builds using the new Nexus server. I found they broke immediately. The first issue I had was with the jaxws-maven-plugin (version 1.10). I had already deployed this plugin to the "3rd party" repository. Maven2 "finds" the plugin, but, the "dependencies" are missing. Why does the plugin work fine with my local Maven2 repository settings on my workstation... But, has so much trouble when I point my settings to the new Nexus repository. What are the pitfalls I must be aware of when switching from my local ".m2/repository" to the Nexus server? Thankyou for any guidance on this! sd P.S. I am using the suggested settings configuration set forth in the "Maven: the definitive gude" book (chapter 16)...i.e., <settings> <mirrors> <mirror> <!--This is used to direct the public snapshots repo in the profile below over to a different nexus group --> <id>nexus-public-snapshots</id> <mirrorOf>public-snapshots</mirrorOf> <url>http://localhost:8081/nexus/content/groups/public-snapshots</url> </mirror> <mirror> <!--This sends everything else to /public --> <id>nexus</id> <mirrorOf>*</mirrorOf> <url>http://localhost:8081/nexus/content/groups/public</url> </mirror> </mirrors> <profiles> <profile> <id>development</id> <repositories> <repository> <id>central</id> <url>http://central</url> <releases><enabled>true</enabled></releases> <snapshots><enabled>true</enabled></snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>central</id> <url>http://central</url> <releases><enabled>true</enabled></releases> <snapshots><enabled>true</enabled></snapshots> </pluginRepository> </pluginRepositories> </profile> <profile> <!--this profile will allow snapshots to be searched when activated--> <id>public-snapshots</id> <repositories> <repository> <id>public-snapshots</id> <url>http://public-snapshots</url> <releases><enabled>false</enabled></releases> <snapshots><enabled>true</enabled></snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>public-snapshots</id> <url>http://public-snapshots</url> <releases><enabled>false</enabled></releases> <snapshots><enabled>true</enabled></snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <activeProfile>development</activeProfile> </activeProfiles> <servers> <server> <id>releases</id> <username>userid01</username> <password>userid01password</password> </server> <server> <id>snapshots</id> <username>userid01</username> <password>userid01password</password> </server> <server> <id>thirdparty</id> <username>userid01</username> <password>userid01password</password> </server> </servers> </settings> -- View this message in context: http://n2.nabble.com/What-are-the-pitfalls-I-must-be-aware-of-when-switching-from-my-local-%22.m2-repository%22-to-the-Nexus-server--tp842540p842540.html Sent from the maven users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]