Re: Merging in our Aether and Guice changes to Maven 3.x

2010-08-03 Thread Jason van Zyl
On Aug 3, 2010, at 9:52 PM, Brett Porter wrote: > > On 04/08/2010, at 4:21 AM, Jason van Zyl wrote: > >> Hi, >> >> We have two major pieces that we, Sonatype, would like to merge into Maven >> 3.x trunk. > > Are these reviewable distinctly? I only seem them mashed together in > Benjamin's f

Re: Merging in our Aether and Guice changes to Maven 3.x

2010-08-03 Thread Brett Porter
On 04/08/2010, at 4:21 AM, Jason van Zyl wrote: > Hi, > > We have two major pieces that we, Sonatype, would like to merge into Maven > 3.x trunk. Are these reviewable distinctly? I only seem them mashed together in Benjamin's fork. > > The first are the Guice changes that we've been talking

Re: Merging in our Aether and Guice changes to Maven 3.x

2010-08-03 Thread Brian Fox
> > > Our ITs say the codebases behave in an equivalent fashion, but it's the > Aether/Guice changes that will be with us for the long >haul. I would rather > wait to integrate those in order to suss out problems that may be a result of > that integration. I think you meant you would rather _no

Re: Merging in our Aether and Guice changes to Maven 3.x

2010-08-03 Thread Jason van Zyl
On Aug 3, 2010, at 6:18 PM, Paul Benedict wrote: > Jason, I think it would be more appropriate to get out beta-2 in its current > state. The new Guice/Aether contributions would be a significant enhancement > and are better suited for beta-3, as far as I see it. Waiting allows you to > continue g

Re: Merging in our Aether and Guice changes to Maven 3.x

2010-08-03 Thread Paul Benedict
Jason, I think it would be more appropriate to get out beta-2 in its current state. The new Guice/Aether contributions would be a significant enhancement and are better suited for beta-3, as far as I see it. Waiting allows you to continue getting feedback from regressions introduced in beta-2 while

Re: Merging in our Aether and Guice changes to Maven 3.x

2010-08-03 Thread Jason van Zyl
On Aug 3, 2010, at 3:20 PM, Olivier Lamy wrote: > Hi, > No particular objections. > The site plugin branch for maven 3 now fail. (I haven't time to debug it > more). > After the merge, how long will we have to add some "hack" to make it work ? > I don't think there's any particular rush. If you

Re: Merging in our Aether and Guice changes to Maven 3.x

2010-08-03 Thread Olivier Lamy
Hi, No particular objections. The site plugin branch for maven 3 now fail. (I haven't time to debug it more). After the merge, how long will we have to add some "hack" to make it work ? 2010/8/3 Benjamin Bentmann : > Jason van Zyl wrote: > >> At any rate we would like to merge these changes in and

Re: Merging in our Aether and Guice changes to Maven 3.x

2010-08-03 Thread Benjamin Bentmann
Jason van Zyl wrote: At any rate we would like to merge these changes in and make plans to release 3.0-beta-2. Just in case, those changes currently live at http://github.com/bentmann/maven-3/ Benjamin - To unsubscribe, e-

Merging in our Aether and Guice changes to Maven 3.x

2010-08-03 Thread Jason van Zyl
Hi, We have two major pieces that we, Sonatype, would like to merge into Maven 3.x trunk. The first are the Guice changes that we've been talking about for a while, and the second is the introduction of Aether which is our second attempt at a stand-alone repository API. The PMC is aware of Aet

maven dependency plugin activity

2010-08-03 Thread Dominique Jean-Prost
Hello, As I'm eagerly waiting for some enhancement in dependency plugin, I would like to know if someone is still involved in the developement of this plugin. I would like some informations, if possible, about MDEP-152 and MDEP-166. Best regards, Dom -- View this message in context: http: