Re: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-16 Thread Brett Porter
@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

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-16 Thread Lee Thompson
On Sun, January 16, 2011 4:43:18 PM Brett wrote 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/ As far as I know there are no guarantees about whether the Aether API will remain

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-16 Thread Brett Porter
On 17/01/2011, at 1:20 PM, Lee Thompson wrote: On Sun, January 16, 2011 4:43:18 PM Brett wrote 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/ As far as I know there are no

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-15 Thread Lee Thompson
Sonatype writeup on Maven 3.x APIs showed up http://www.sonatype.com/people/2011/01/how-to-use-aether-in-maven-plugins/ 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

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-05 Thread Lee Thompson
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

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-04 Thread Brett Porter
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

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-03 Thread Lee Thompson
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

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-03 Thread Anders Hammar
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

Re: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-03 Thread Lee Thompson
@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

RE: [mojo-dev] Mojo Developer Cookbook and v3.0

2011-01-03 Thread Robert Scholte
@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