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... > > >
