[VOTE] Release Apache Maven Plugin Tools version 3.5.1

Hi, We solved 15 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12338196&styleName=Text There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20status%20%3D%20Open%20ORDER%20BY%2

AtEnd aggregation implementation idiom broken

I've run across multiple broken plugins that follow the deployAtEnd implementation found in the deploy plugin.  The intent is to delay an action until the end of the aggregation cycle.  In the current implementation, there are multiple problems; 1. If one or more of the aggregated modules ski

Re: parallelise not overlapping tasks

Hi Robert, this is the gradle way but it only works because you also have the dependency chain between plugins in gradle. This is missing in maven (like group:artifact@execution before group':artifact'@execution' / or after) and therefore can't be worked out at all with just inputs outputs for bac

Re: parallelise not overlapping tasks

Hi Romain, I don't think this is something for the pom. It is the plugin which should know if it has effect on the build. Or maybe more global: if we could define for the plugin what is input and what is output, then it should be possible to decide which parts could run in parallel. thanks,

parallelise not overlapping tasks

Hi guys, there is no way to parallelize not conflicting tasks for a same phase at the moment right? Any way it gets under the radar? A common example is to run all code analyzis concurrently (findbugs, pmd, checkstyle, ...) at the same time without waiting for one then the other etc since all can

cdi-api leaking?

Hi guys, cdi-api is still in maven lib and breaks any plugin using it since it is an old version, can it be dropped or at least isolated from plugin classloaders? Thanks, Romain Manni-Bucau @rmannibucau | Blog | Old Blog