Benson, I think you got this completely wrong. I don't care about the eclipse policies. But IF eclipse says they like to change the package names, then WE have to change all our aether imports and retest all that stuff...
If it stays com.sonatype, then otoh we don't need to do much... LieGrue, strub --- On Thu, 8/18/11, Benson Margulies <bimargul...@gmail.com> wrote: > From: Benson Margulies <bimargul...@gmail.com> > Subject: Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core > with EPL licenses - take 2 > To: "Maven Developers List" <dev@maven.apache.org> > Date: Thursday, August 18, 2011, 1:17 PM > Mark, Can it possibly matter what the > java package names are? There > are ton's of wierd historical package names floating around > the > universe. There is no requirement for incubating Apache > projects to > move package names just for the sake of moving them. I > think that > 'sonatype' in a package name is a herring of perfect > redness. > > > On Thu, Aug 18, 2011 at 8:59 AM, Mark Struberg <strub...@yahoo.de> > wrote: > > Jason, Brian, Benjamin or any other person involved, > > > > Before voting on this issue, I'd like to get an idea > what it means for us. So please allow me a few questions: > > > > a.) how can appache maven committers anticipate on > aether over at Eclipse? What if someone (like me) likes to > contribute, but wants to make sure that his contributions > are also possible to release separately under ALv2? > > > > b.) is it possible to operate aether without sisu? > Pure JSR-330 and/or plexus DI stuff is fine. Is there any > direct guice depending code in aether? > > > > c.) will the package names remain com.sonatype or will > they get changed to org.eclipse.*? This is important for us > to know. If so, we can just cancel the vote and wait for > this stuff to be released at Eclipse. > > > > d.) How long will it take to get the first aether > release done at Eclipse? > > > > If there is a chilly way for maven committers to get > involved with that stuff over at Eclipse, then this would be > a big pro. > > > > txs and LieGrue, > > strub > > > > > > --- On Thu, 8/18/11, Anders Hammar <and...@hammar.net> > wrote: > > > >> From: Anders Hammar <and...@hammar.net> > >> Subject: Re: [VOTE] Usage of Aether and Sisu as > dependencies of maven core with EPL licenses - take 2 > >> To: "Maven Developers List" <dev@maven.apache.org> > >> Date: Thursday, August 18, 2011, 10:56 AM > >> +1 (non-binding) > >> > >> /Anders > >> > >> 2011/8/18 Arnaud Héritier <aherit...@gmail.com>: > >> > Hi all, > >> > > >> > Thus as decided with Mark and Kristian I > relaunch a > >> new vote with a better > >> > scope about what we are voting for. > >> > > >> > Next releases of SISU and Aether will be > released at > >> Eclipse.org under EPL > >> > 1.0 license. > >> > Before they were published under ASL or > dual ASL/EPL > >> licenses thus as > >> > defined in our policy [1] this change put > them in > >> Category B [2] and we need > >> > to validate this change by a vote with a > majority of > >> the PMC in favor (but > >> > the vote is open to everybody). > >> > I push only one vote for both dependencies > as for > >> now I see no reason to > >> > accept one and not the other. > >> > This vote will be open for 6 days as we are > in > >> august (If we have not > >> > enough votes at the end of next wednesday > will see if > >> we really need to > >> > extend it). > >> > > >> > The vote : > >> > > >> > [+1] I'm in favor to use as Maven core > dependencies > >> SISU and AETHER libraries > >> > published under EPL 1.0 License and released > under > >> eclipse.org governance > >> > [+0] No opinion, do what you want. > >> > [-1] I'm against because .... (please > elaborate) > >> > > >> > Arnaud > >> > > >> > [1] http://maven.apache.org/developers/dependency-policies.html > >> > [2] http://www.apache.org/legal/resolved.html#category-b > >> > > >> > >> > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
