+1 (non-binding) We have started to use Aether in the upcoming Maven Android Plugin and it already fixes a bunch of issues related to inclusion of native dependencies.
And as a user I am concerned that Maven needs to keep moving forward asap to avoid more mindshare loss on cutting edge/power users side and not taking aether and sisu in would slow the project down even more. manfred http://simpligility.com On Wed, August 17, 2011 7:19 am, Arnaud HERITIER wrote: > Hi all, > > Next releases of SISU and Aether will be done 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 1 week 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. > [+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: [email protected] For additional commands, e-mail: [email protected]
