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? Lee ________________________________ From: Robert Scholte <rfscho...@codehaus.org> To: dev@mojo.codehaus.org Sent: Mon, January 3, 2011 1:37:21 PM Subject: RE: [mojo-dev] Mojo Developer Cookbook and v3.0 Hi Lee, I did already notice you were moving this project to M3. IMHO I think we should try to support as many Maven versions as possible. It's not just up to us to force developers to move to the most recent version of Maven. For instance: companies might have locked their Maven version for certain projects. Reasons to move to a newer version of Maven would be: - Bugs in Maven which might cause the plugin to fail. - Maven-API changes which are required for certain fixes/improvements of the plugin. btw, this counts for any type of newer versions (major-updates, minor-updates, incremental-updates). I hope you have good reason to switch to M3, but I'd suggest to depend on Maven 3.0 instead of 3.0.1 (unless one of the above reasons forces you to use 3.0.1) -Robert ________________________________ Date: Mon, 3 Jan 2011 10:56:01 -0800 From: bm...@yahoo.com To: dev@mojo.codehaus.org Subject: Re: [mojo-dev] Mojo Developer Cookbook and v3.0 Yeah, my environment is all maven 3.0.1. I just converted all my plugins to use as little the maven-compat aspects as possible. Any other mojos doing this yet? If not, it might explain the lack of docs. ________________________________ From: Anders Hammar <and...@hammar.net> To: dev@mojo.codehaus.org Sent: Mon, January 3, 2011 12:31:04 PM Subject: Re: [mojo-dev] Mojo Developer Cookbook and v3.0 Using Aether directly will make your plugin require Maven 3.x. /Anders On Mon, Jan 3, 2011 at 19:18, Lee Thompson <bm...@yahoo.com> wrote: ArtifactFactory out, Aether in? Long live Aether? >http://www.sonatype.com/people/2010/08/introducing-aether/ > > > ________________________________ From: Lee Thompson <bm...@yahoo.com> >To: dev@mojo.codehaus.org >Sent: Thu, December 30, 2010 8:28:07 PM >Subject: [mojo-dev] Mojo Developer Cookbook and v3.0 > > >So, a bunch of the API's used in the Mojo Developers Cookbook have been marked >"deprecated" in maven 3.0. ArtifactFactory and ArtifactMetadataSource for >instance. > > http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook > >Another one I use a lot is WagonManager. > >I poked around the maven source code for about an hour and couldn't figure out >what replaces ArtifactFactory. Anyone else going to Maven 3.0 run into this >or >just ignore the warnings... > > >
