So my current plan is to roll in Christian's change, and then I'm going to roll the 3.2.2.
If anyone wants to work on anything else speak up. I'm in no rush but I have time this weekend so I'll roll the 3.2.2 if no one else is going to work on anything. My next project is to write a validator that compares what Aether resolves, what it looks like after the project filter is applied, and what that looks like in the WAR, Assembly, and Dependency plugin. There are a whole raft of issues where there are claimed scope transition issues but it's not easy for a user to see what's actually resolved vs what a plugin might do if it employes its own resolution or artifact filtering. I've already found one case where the WAR plugin isn't doing the right thing so I'm just going to make a tool to split out everything along the way so I can see what system is at fault and then try to fix the problems, or assign them to the respective plugin. On Jun 12, 2014, at 8:05 AM, Jason van Zyl <[email protected]> wrote: > Git and Github especially get credit. If there is a PR for core with tests > and a corresponding PR for the integration tests and it all applies and > passes as per [1] then it makes reviewing so, so much easier. > > The next set of validation I'd like to do is make sure that all of m2e work > with any of these changes. If this works then incorporating changes becomes > radically easier. Working on these PRs has been very pleasant. Maybe not for > the contributors whose PRs I erased by mistake. Konstantin was particularly > patient. > > [1]: http://takari.io/2014/06/02/contributing-to-maven-core.html > > On Jun 12, 2014, at 5:15 AM, Michael-O <[email protected]> wrote: > >> >>> I'm going to look at a couple more issues, but I'm done processing all the >>> pull requests and I will look at cutting a release over the weekend. >>> >>> Thanks to all of those who contributed pull requests for core! The highest >>> level of participation I've seen in a long time. >> >> I think this credit goes to Github. It eases the participation of >> non-committers tremendously. Though, we need to improve the PR process on >> mirrored repos. >> >> Mike >> >> --------------------------------------------------------------------- >> 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 > http://twitter.com/takari_io > --------------------------------------------------------- > > A man enjoys his work when he understands the whole and when he > is responsible for the quality of the whole > > -- Christopher Alexander, A Pattern Language > > > > > > > > > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io --------------------------------------------------------- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
