Re: Maven moving to the next level: the build/consumer pom

2020-07-05 Thread Robert Scholte
That is actually the first reference of my original e-mail: simple-parent with the simple-weather + simple-webapp. I've added as an integration-test to ensure all these features work as expected. The expected-folder contains what I expect to be installed to the local repository. Robert [1]  ht

Re: Maven moving to the next level: the build/consumer pom

2020-07-05 Thread Hervé BOUTEMY
I just created "buildconsumer" branch for Maven Archetype: https://github.com/apache/maven-archetype/tree/buildconsumer CLI building with Maven 3.6.3 expectedly breaks: $ mvn verify -Drevlist=test [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the P

Re: custom default lifecycle per project

2020-07-05 Thread Romain Manni-Bucau
Here is a sample public build: https://github.com/talend/component-runtime Interesting modules are - just listing one per type - if master looks weird tag 1.1.19 can be a fallback: 1. https://github.com/Talend/component-runtime/blob/master/component-starter-server/pom.xml 2. https://github.com/Tal

Re: Maven moving to the next level: the build/consumer pom

2020-07-05 Thread Hervé BOUTEMY
idea: why not create a branch in one or multiple Maven multi-module builds that will show the new features (no parent version, no version for reactor, and I don't know what else) I suppose creating such branches in maven-archetype, maven-plugin-tools, Maven core itself, would not be hard and wo

Re: custom default lifecycle per project

2020-07-05 Thread Hervé BOUTEMY
Le samedi 4 juillet 2020, 23:15:19 CEST Romain Manni-Bucau a écrit : > Le sam. 4 juil. 2020 à 18:09, Stephen Connolly < > > stephen.alan.conno...@gmail.com> a écrit : > > On Sat 4 Jul 2020 at 16:54, Romain Manni-Bucau > > > > wrote: > > > Le sam. 4 juil. 2020 à 16:38, Stephen Connolly < > > > >