On 16/01/2011, at 3:32 PM, Lee Thompson wrote: > Sonatype writeup on Maven 3.x APIs showed up > http://www.sonatype.com/people/2011/01/how-to-use-aether-in-maven-plugins/ >
I'll take that up with the maven list, but that's surprising given the first two paragraphs here: http://mail-archives.apache.org/mod_mbox/maven-dev/201008.mbox/%3cb00d71d7-8a8e-4db2-bb99-725bf0f01...@apache.org%3E As far as I know there are no guarantees about whether the Aether API will remain stable across versions. Use it in your plugins at your own risk. - Brett > From: Lee Thompson <bm...@yahoo.com> > To: dev@mojo.codehaus.org > Sent: Wed, January 5, 2011 5:30:27 PM > Subject: Re: [mojo-dev] Mojo Developer Cookbook and v3.0 > > > On Tue, January 4, 2011 9:25:24 PM, Brett said: > 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. > > Thanks Brett. Shorter term then, with many of the maven 2 API's marked > deprecated in Maven 3.0, it would be good to know which APIs we should ignore > the warnings and press on and which APIs have alternative implementations. > ArtifactFactory for instance. > > http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook > > A quick note in the wiki would be great. > > > > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
