On Sun 23 Dec 2018 at 11:32, Michael Osipov <micha...@apache.org> wrote:
> Am 2018-12-23 um 11:14 schrieb Stephen Connolly: > > Over the break I *may* get some time to work on the tooling improvements > > that Robert, Hervé and I identified for the jump to 4.0.0 (namely a > better > > way to ensure api binary compatibility for the APIs that core exposes to > > plugins) > > > > If I do get a chance to work on this, it’ll be in a branch until we think > > it’s “good enough”. > > > > The idea is to enable large scale lambdafication and other Java 8 > > improvements in core without breaking plugins. > > I'd rather see a big bug/PR sweep than lambafication which does not give > a huge benefit for the users. What else I'd like to see is edge cases > covered Christian Schulte started to work on. We can break things this > time and clean them up. We need to get people actually involved in the code. Lambdafication and other modernisation refactoring enable people to get their hands dirty without committing too much. Asking potential new blood to look at the harder things will not get us new blood. Actual committers should be looking at the other changes... though I don’t believe we can change the pom until 5.0.0 which is why the scope of 4.0.0 is likely: * modernise the codebase * Java 8 baseline * perhaps relocate aether to org.apache.maven * other behaviour changes that do not affect the pom * nicer failure message when presented with a newer modelVersion * native consumer pom support... perhaps also PDT publishing > > Michael > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
