t;
> -Ursprüngliche Nachricht-
> Von: Robert Scholte [mailto:rfscho...@apache.org]
> Gesendet: Montag, 13. April 2020 21:39
> An: dev@maven.apache.org
> Betreff: Re: AW: Maven intern projects
>
> the problem is that with every folder you'll need a separate execution-b
An: dev@maven.apache.org
Betreff: Re: AW: Maven intern projects
the problem is that with every folder you'll need a separate execution-block of
the maven-compiler-plugin.
I've tried to solve within a single execution block, but that made it worse and
impossible to manage.
In the en
the problem is that with every folder you'll need a separate execution-block of
the maven-compiler-plugin.
I've tried to solve within a single execution block, but that made it worse and
impossible to manage.
In the end having 1 execution block for every javac call makes sense.
Multirelease jar
What users finally expect is to have multirelease JAR building being a Maven
native functionality. This means, it should be as-easy-as putting code in these
folders:
src/main/java/9/
src/main/java/
src/main/java/11/
then perform
mvn clean package
to get a multi-release jar -- without *any* sp
Great to hear!
Here is my personal wish list. ;-)
IMHO generally a good idea is to provide public releases of all maven plugins
and mojohouse plugins which had not been release within 12 months, so we all
can get rid of depending on -SNAPSHOTs and private forks. :-)
When asking for featu
