On 05/01/2011, at 5:09 AM, Lee Thompson wrote: > I agree with you! > > I'd add another point, you are upgrading as you are going to add new > capabilities into your plugin that Maven 2.x won't allow. > > What drove the Maven 3.x rewrite is I'm interested in re-introducing some > functionality that I deprecated due to that function getting developed to a > maven snapshot back in late '06 or early '07. > > Poking around, it looks like Juice (and Aether) are full citizens in Maven > 3.0. Writing a Mojo for maven 3.x could be a completely different animal > than Maven 2.x. If a Mojo were a Juice component, it certainly would be > easier to test. No ArtifactFactory, no Plexus?
The currently supported APIs in Maven 3 are the same as in Maven 2, including the mojo annotations (which are not Plexus annotations). There's some talk about expanding the plugin API in future releases to enumerate a supported API for all these things, but it's not intended that you depend on Guice or Aether directly. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
