Brian Fox wrote: > The separate builds are using separate local repos. Everything should be > built and deployed to nexus so that should have the latest
Hm, not sure I understand you correctly. The log file of the first IT build [0] reads > [INFO] snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.5-SNAPSHOT: > checking for updates from central > [INFO] snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.5-SNAPSHOT: > checking for updates from codehaus.snapshots > Downloading: > http://localhost:8081/content/groups/public/org/apache/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin-2.5-20080726.211140-49.pom > 9K downloaded > Downloading: > http://localhost:8081/content/groups/public/org/apache/maven/plugins/maven-javadoc-plugin/2.5-SNAPSHOT/maven-javadoc-plugin-2.5-20080726.211140-49.jar > 122K downloaded The URL http://localhost:8081/content/groups/public is the Nexus facade for central, isn't it? I mean it looks like it's neither using the artifact from the plugin's IT repo nor from the local repo of the Hudson job but getting it from remote which is not intended. I have now switched back to use the install:install-file goal to stage the plugin into the IT repo which seemed to work locally. I hope Hudson will agree by the next build #115 (never knew CI is that exciting ;-) ) Benjamin [0] https://ci.sonatype.org/job/Maven-Plugins/ws/trunk/maven-javadoc-plugin/src/it/MJAVADOC-110/build.log/*view*/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
