In my projects, the most plugins use single execution.
External projects also have this kind of principle.
Thus we should have a look in those possibilities where the most plugins
can gain the performance.
Usually the compiler and tests take long.
I know that maven-compiler-plugin:3.8.1 will be inc
What about having parallel 'planes' of execution?
Stuff like checktyle, rat, validation plugin may run in their own plane of
execution.
By default every existing plugin will be on a 'default' plane.
When the build starts we start a thread/fork a process for each plane used
by plugins declared in th
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
Hello Apache projects,
I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
mon
Hi all,
In my intent to improve m2e, I realize that one key criteria of
sustainability for m2e project is the ability to interact well with Maven
project (interacting more with the community, trying snapshots, identifying
breaking or major issues, consolidating the non-CLI usage of Maven as
APIs..
