On 11/10/2010, at 5:42 PM, Jason Chaffee wrote: > Yes. > > The 2.2.1 is configured in the parent pom dependencyMangement. > > I remember Jason saying talking about the Artifact refactoring about a year > ago and saying it would not be backwards compatible with 2.0 and that if you > had plugins using Artifact resolution you would need to rewrite them in 3.0. > That is why I thought this particular plugin is failing. I tagged it as > something I would need to refactor with 3.0. > > Is this no longer the case with 3.0?
Nope, that was never the case on trunk. For example, the Compiler plugin depends on 2.0.6 APIs for maven-artifact and maven-core. Something is wrong in the way that it is loading your libraries - maybe running with -X will show how it constructs the plugin's dependencies and point to the issue. You could also try re-compiling the plugin with Maven 3, see if it builds, then try using that snapshot and see if it works. That would eliminate a complete incompatibility. > > Even so, it is perplexing as to why a class would not be found in 3.0 but was > found properly in 2.0 with the same plugin jar. This is usually a difference in the way the POM is loaded, and as such the way the the dependency JARs are included in the classloader. The fact that it's Maven ones missing does make it suspicious to the core differences, but it also clearly works in other POMs. Another thing to check is if the dependency POM is more strictly validated and failing (you should see something in the build for that), or if there are some other potential changes like an <exclusion> for one of those libraries in the tree, or a <optional> flag. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
