Hi,
The problem is most likely with the plugin prefix mapping. The findbugs
plugin is not using the standard maven-${prefix}-plugin convention (see:
http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html)
and requires metadata help to get to the custom plugin artifactId from the
plugin prefix. Notice how in your first output where it fails the request is
trying with '*maven-findbugs-plugin*' as the artifactId, while the
successful resolution uses the correct name '*findbugs-maven-plugin*'.
Essentially what I suspect happens for the Hudson build is that it cannot
map the 'findbugs' plugin prefix to the plugin coordinates. So, I expect
that if you temporarily move aside all the 'maven-metadata-*.xml' files
directly under '/org/codehaus/mojo' in the local .m2 repository of the user
the build will start failing too. The simplest workaround for this now would
be to use the full plugin coordinates for invoking the plugin (rather than
using the prefix).
This may be a regression in the way we merge plugin metadata for a virtual
repository, so we will look into this and let you know.
Thanks,
Yoav
On Wed, Apr 14, 2010 at 10:38 PM, Chris Law <[email protected]> wrote:
>
> Well, as I said before, the effective POMs for the two users are identical,
> including all the repositories. The settings.xml files have the same
> mirror
> element.
>
> But my main concern is that this worked with Artifactory 2.1/Java 6.0.11,
> although we were experiencing such bad performance that the deploys would
> often fail our Hudson builds. So I upgraded to Artifactory 2.2.2 and Java
> 6.0.18, without changing anything on the Hudson server.
>
> I guess I just have to dig deeper. Thanks again for the help.
>
> --
> View this message in context:
> http://n2.nabble.com/Upd-from-2-1-to-2-2-2-now-Hudson-builds-fail-on-findbugs-tp4901326p4903684.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
>
--
Yoav Landman
CTO, JFrog Ltd.
Artifactory Creator
http://www.jfrog.org/
------------------------------------------------------------------------------
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
