Hi Brian As least "jaxws-tools.jar" is missing, and *apparently* several other jars that are included in the jaxws-ri lib.
(see "https://jax-ws-commons.dev.java.net/jaxws-maven-plugin/dependencies.html";) It was not necessary to manually upload any extra dependencies to my ".m2/repository". I guess I'm just trying to determine what "extra steps" I have to take to have my maven builds work using this new Nexus repository manager. I had assumed -- perhaps incorrectly -- that if my maven builds worked on my local workstation using my local ".m2/repository", etc, then, they should work equally well when using the Nexus repository manager, etc Since this is apparently not the case, I'd like some suggestions on what issues I should expect after transitioning and how to fix them. Here is a copy of a test project pom...(below) (All I'm trying to do in this test is run the "jaxws-maven-plugin" to generate java binding classes for a simple wsdl) <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <modelVersion>4.0.0</modelVersion> <groupId>test.jaxws.maven.plugin</groupId> <artifactId>main</artifactId> <packaging>jar</packaging> <version>0.0.1-SNAPSHOT</version> <name>main</name> <url>http://maven.apache.org</url> <repositories> <repository> <id>maven2-repository.dev.java.net</id> <name>Java.net Maven 2 Repository</name> <url>http://download.java.net/maven/2</url> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>maven2-repository.dev.java.net</id> <name>Java.net Maven 2 Repository</name> <url>http://download.java.net/maven/2</url> </pluginRepository> </pluginRepositories> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> <dependency> <groupId>com.sun.xml.ws</groupId> <artifactId>jaxws-rt</artifactId> <version>2.1.3</version> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>jaxws-maven-plugin</artifactId> <version>1.10</version> <executions> <execution> <phase>generate-sources</phase> <goals> <goal>wsimport</goal> </goals> </execution> </executions> <configuration> <sourceDestDir>C:/testjaxwsplugin/main/src/main/java</sourceDestDir> <wsdlDirectory>C:/testjaxwsplugin/main/src/main/resources</wsdlDirectory> <verbose>true</verbose> </configuration> </plugin> <plugin> <inherited>true</inherited> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.5</source> <target>1.5</target> </configuration> </plugin> </plugins> </build> </project> Brian E. Fox wrote: > > It finds the plugin but not the dependencies. Where are these > dependencies? Are they also in the 3rd party repo? Do you have any > routing rules defined that may exclude the 3rd party repo for these > dependencies? > > If you can paste the logs, it would help. I would recommend bringing the > discussion over to [EMAIL PROTECTED] > > -----Original Message----- > From: sairndain [mailto:[EMAIL PROTECTED] > Sent: Friday, September 05, 2008 10:42 PM > To: [email protected] > Subject: What are the pitfalls I must be aware of when switching from my > local ".m2/repository" to the Nexus server? > > > 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-switc > hing-from-my-local-%22.m2-repository%22-to-the-Nexus-server--tp842540p84 > 2540.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] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- 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--tp842540p842606.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]
