I'm kind of against includes and import... I favour mix-ins as the solution to that set of problems...
Additionally I see all the "hacks" people have evolved as been significantly less relevant with PDTs including both ranges and hints as well as the provides and supports declarations... but yes we need to address what we see as the "resolution" of these issues is in the 5.0.0+ world On Sunday 16 October 2016, Christofer Dutz <christofer.d...@c-ware.de> wrote: > Hi guys, > > > I just wanted to add one thing to the list: > > https://issues.apache.org/jira/browse/MNG-6107 > > But I can't edit or comment on the page: > > https://cwiki.apache.org/confluence/display/MAVEN/POM+Model+Version+5.0.0 > > > Chris > > ________________________________ > Von: Stephen Connolly <stephen.alan.conno...@gmail.com <javascript:;>> > Gesendet: Sonntag, 16. Oktober 2016 13:33:29 > An: Maven Developers List > Betreff: Re: Some thoughts on Maven 5 > > Adding a section to the wiki to help track this > > https://cwiki.apache.org/confluence/display/MAVEN/POM+Model+Version+5.0.0 > > On 16 October 2016 at 04:12, Christian Schulte <c...@schulte.it > <javascript:;>> wrote: > > > Am 10/16/16 um 02:03 schrieb Stephen Connolly: > > >> On 16 Oct 2016, at 00:07, Christian Schulte <c...@schulte.it > <javascript:;>> wrote: > > >> Any thoughts about how to name that new build pom? > > > > > > project.mvn or pom.mvn > > > > > > But only if we move to a non-xml DSL > > > > > > If we are still XML then I say stick with pom.xml and sniff the > > modelVersion > > > > +1 > > > > Being able to build all Maven 2+ kinds of projects using Maven 5+ would > > be cool. It's not a must have in my opinion. If this would degrade the > > possibilities of Maven 5+, I'd say it's worth giving up on it. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org <javascript:;> > > For additional commands, e-mail: dev-h...@maven.apache.org > <javascript:;> > > > > > -- Sent from my phone
