OK, So, the plot thickens :) The issue looks like it's related to maven plugin group definition? The hudson user try to find "org/apache/maven/plugins/maven-findbugs-plugin" while your user is looking for "org/codehaus/mojo/findbugs-maven-plugin". I suggest you look in the settings.xml if you find plugin group declarations and some differences? Anyway, to solve it for good, you can declare the maven findbugs plugin you want with the good version in a pluginManagement block of your POM.
Hope this help, Fred. On Wed, Apr 14, 2010 at 6:18 PM, Chris Law <[email protected]> wrote: > > I deleted findbugs-maven-plugin directory from the Hudson user's local > repository, > but it still failed. Artifactory's request log showed: > > 20100414102027|750|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/apache/maven/plugins/maven-metadata.xml|HTTP/1.1|404|0 > 20100414102027|531|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/apache/maven/plugins/maven-metadata.xml|HTTP/1.1|404|0 > 20100414102027|422|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/maven-metadata.xml|HTTP/1.1|200|399 > 20100414102028|110|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/maven-metadata.xml.sha1|HTTP/1.1|200|40 > 20100414102028|125|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/maven-metadata.xml|HTTP/1.1|200|399 > 20100414102028|141|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/maven-metadata.xml.sha1|HTTP/1.1|200|40 > 20100414102028|281|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/apache/maven/plugins/maven-findbugs-plugin/maven-metadata.xml|HTTP/1.1|404|0 > 20100414102028|16|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/apache/maven/plugins/maven-findbugs-plugin/maven-metadata.xml|HTTP/1.1|404|0 > > I then deleted the findbugs-maven-plugin directory from my local repository > and tried the same command, which worked. The request.log: > > 20100414104157|765|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/findbugs-maven-plugin/maven-metadata.xml|HTTP/1.1|200|680 > 20100414104157|31|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/findbugs-maven-plugin/maven-metadata.xml.sha1|HTTP/1.1|200|40 > 20100414104157|78|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/findbugs-maven-plugin/maven-metadata.xml|HTTP/1.1|200|680 > 20100414104157|31|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/findbugs-maven-plugin/maven-metadata.xml.sha1|HTTP/1.1|200|40 > 20100414104157|16|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/findbugs-maven-plugin/2.3.1/findbugs-maven-plugin-2.3.1.pom|HTTP/1.1|200|11521 > 20100414104157|31|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/findbugs-maven-plugin/2.3.1/findbugs-maven-plugin-2.3.1.pom.sha1|HTTP/1.1|200|40 > 20100414104157|0|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/findbugs-maven-plugin/2.3.1/findbugs-maven-plugin-2.3.1.jar|HTTP/1.1|200|113452 > 20100414104157|0|REQUEST|172.22.27.89|non_authenticated_user|GET|/repo/org/codehaus/mojo/findbugs-maven-plugin/2.3.1/findbugs-maven-plugin-2.3.1.jar.sha1|HTTP/1.1|200|40 > > By the way, for my testing, I'm not using Hudson but logging in as Hudson's > build user. > > I don't understand why the Hudson user's requests try to get metadata from > org.apache.maven.plugins, while my user's requests are only for > org.codehaus/mojo/findbugs-maven-plugin, > nor why Hudson's request is restricted to org.codehaus.mojo without the > findbugs-maven-plugin. > > Shouldn't two users with the same effective POMs on the same machine running > the same Maven commands on the same project exhibit the same behavior, at > least to the point of resolving a dependency? > > -- > View this message in context: > http://n2.nabble.com/Upd-from-2-1-to-2-2-2-now-Hudson-builds-fail-on-findbugs-tp4901326p4902236.html > Sent from the Artifactory - Users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users > -- Co. Founder and Chief Architect JFrog Ltd http://www.jfrog.org/ http://twitter.com/freddy33 ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
