Yes, it all works fine and the tests pass. On Nov 10, 2011, at 10:38 AM, Olivier Lamy wrote:
> Ok I will start a vote for both aether and sisu upgrade. > > Just tested today both. Just need a simple change to have unit tests passed. > > > 2011/11/10 Jason van Zyl <[email protected]>: >> Sure, I'll let someone the PMC call the vote. Happy to do the work once >> that's taken care of. >> >> On Nov 10, 2011, at 9:08 AM, Stephen Connolly wrote: >> >>> I'm fine, but process says you should call a vote to change the >>> dependency from the ASL version to the EPL licensed version. Yes there >>> was a vote before, but the circumstances have changed, and hence there >>> is strong likelyhood (IMHO) that a re-vote might result in a different >>> answer >>> >>> -Stephen >>> >>> On 10 November 2011 13:50, Jason van Zyl <[email protected]> wrote: >>>> So are people fine with using Aether 1.13. I've already got the necessary >>>> changes if we want to go ahead with that. >>>> >>>> On Nov 8, 2011, at 12:50 PM, Jason van Zyl wrote: >>>> >>>>> >>>>> On Nov 8, 2011, at 12:15 AM, Brett Porter wrote: >>>>> >>>>>> >>>>>> On 07/11/2011, at 8:43 AM, Jason van Zyl wrote: >>>>>> >>>>>>> You guys decided you wanted to wait so let's just wait. I didn't think >>>>>>> it would take this long to get through either but it is what it is. So >>>>>>> realistically we're looking at 3.0.4 in 4 weeks. >>>>>> >>>>>> But it could also be longer. >>>>>> >>>>> >>>>> Yes, but that's the decision you made. >>>>> >>>>>> I don't see why we should treat the existing EPL release any differently >>>>>> than if it were to be released from Eclipse at this point. >>>>> >>>>> Yes, I tried to explain this a month ago. The code is all Sonatype >>>>> copyright, and EPL. Wherever the code is that fact remains the same. >>>>> >>>>>> Going to Eclipse is a positive step from now, there will be better >>>>>> transparency and governance, but arriving there is not the end of the >>>>>> road. It's going to be even longer that it is more diverse, graduates >>>>>> the incubator there, and becomes just consumable as a dependency. >>>>>> >>>>>> If someone wants to do a 3.0.4 release, they should do it, whether that >>>>>> doesn't include this fix, or delivers it as a patch on the version we're >>>>>> using, or uses the EPL version from Github. If nobody is prepared to do >>>>>> a release now, that's fine too, but they shouldn't have to sit around >>>>>> waiting. The whole reason I was concerned about Aether in the first >>>>>> place was because we'd get stuck not being able to ship a fix to Maven >>>>>> without getting around another project - we can't let ourselves get into >>>>>> that position. >>>>>> >>>>>> In my ideal world, Benjamin would cherry-pick the fix he's already made >>>>>> for the issue Mark is concerned about, release 1.11.1, and we upgrade >>>>>> and someone releases Maven 3.0.4. That wouldn't take long, wouldn't >>>>>> change the direction everything is going, and let everyone get on with >>>>>> it. >>>>>> >>>>>> Is there a reason we shouldn't do that? >>>>>> >>>>> >>>>> Because it's far more work than necessary, use Aether 1.13 that is EPL >>>>> and is released. I can update it and start the release process tomorrow. >>>>> >>>>>> Cheers, >>>>>> Brett >>>>>> >>>>>> -- >>>>>> Brett Porter >>>>>> [email protected] >>>>>> http://brettporter.wordpress.com/ >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>> >>>>> Thanks, >>>>> >>>>> Jason >>>>> >>>>> ---------------------------------------------------------- >>>>> Jason van Zyl >>>>> Founder, Apache Maven >>>>> http://twitter.com/jvanzyl >>>>> --------------------------------------------------------- >>>>> >>>>> Our achievements speak for themselves. What we have to keep track >>>>> of are our failures, discouragements and doubts. We tend to forget >>>>> the past difficulties, the many false starts, and the painful >>>>> groping. We see our past achievements as the end result of a >>>>> clean forward thrust, and our present difficulties as >>>>> signs of decline and decay. >>>>> >>>>> -- Eric Hoffer, Reflections on the Human Condition >>>>> >>>>> >>>>> >>>>> >>>> >>>> Thanks, >>>> >>>> Jason >>>> >>>> ---------------------------------------------------------- >>>> Jason van Zyl >>>> Founder, Apache Maven >>>> http://twitter.com/jvanzyl >>>> --------------------------------------------------------- >>>> >>>> We all have problems. How we deal with them is a measure of our worth. >>>> >>>> -- Unknown >>>> >>>> >>>> >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> Thanks, >> >> Jason >> >> ---------------------------------------------------------- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> --------------------------------------------------------- >> >> >> >> >> >> > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
