t;- build/consumer feature enabled by default
> >- Remove old stuff
> >- break things and improve the build pom ...
> >- Remove maven-compat .. ? introducing maven-compat3 ?..
> >- Maybe JDK 11 base? (LTS?) just a thought
> >-
> >
> > Also making a 3.7.0 before so we can learn things related to
> > build-consumer pom before going to Maven 4.0.0 where we can break
> > things which we can not in 3.7.0 ...
>
> Hi Karl,
>
> I don't think that that we should press such an amount of changes into a
> minor release. If you want to have a 3.7.0 why not branch off 3.6.3 and
> cherry-pick selected changes
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
--
Andreas Aronsson
Mobil: +46 704 566 595
http://www.aron.nu
"I'd rather have friends who care than friends who agree with me."
Arlo Guthrie
It is possible if you are using maven-3.3.1 or newer.
Look at the extension mechanism here
http://takari.io/2015/03/19/core-extensions.html
On Sat 18 Apr 2020, 00:48 Hunter C Payne,
wrote:
> I don't believe it is possible to change the POM during a single build.
> However, are you sure this
