Hi Jason, Txs 4 the answers.
Changing the package names would of course require some more work on both sides, but at the end it might even be better for the long run. For example using the sonatype name in a package might later cause your company troubles/discussions with Trademarks and stuff. Otoh it would require us to go through maven-core and all plugins to change imports. So either way is ok, but we need to know the direction. LieGrue, strub --- On Thu, 8/18/11, Jason van Zyl <ja...@maven.org> wrote: > From: Jason van Zyl <ja...@maven.org> > 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:24 PM > > On Aug 18, 2011, at 8:59 AM, Mark Struberg 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? > > > > The copyright of the code entering Eclipse always remains > that of the author. The code that is submitted to Eclipse > must be under the EPL license, but as the copyright owner > you can make your contributions available under any license > you choose. > > > 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? > > > > Aether requires no DI. > > > 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. > > > > I'm going to ask for an exception. I don't want to change > the package names if I don't have to. It's just a pain in > the ass. > > > d.) How long will it take to get the first aether > release done at Eclipse? > > > > The creation review ends next Wednesday, it will take > another week to provision the project. At that point if we > don't have to change the package names we can do a release. > If we have to change the package names then that will likely > add at least another two weeks for proper testing. > > > 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. > > > > Sorry, I don't grok that sentence. > > > 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 > > > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > --------------------------------------------------------- > > In short, man creates for himself a new religion of a > rational > and technical order to justify his work and to be justified > in it. > > -- Jacques Ellul, The Technological Society > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
