Re: parallelise not overlapping tasks

Yes, in theory. In practise they are partially about sequencing cause maven has nothing else handy (the merge in a multi module project is a headache for most users i met). Also you cant not respect phases today (regarding my impl). Last point is that id the remark was on my last note, this is tri

Re: parallelise not overlapping tasks

phases are about the user calling out how far they want to go, not about sequencing... at least once we get a propper execution graph On Thu, 6 Dec 2018 at 13:54, Romain Manni-Bucau wrote: > Currently maven can't but I expect a way to do it, either in the next xsd > as originally proposed or, wh

Re: parallelise not overlapping tasks

Hi guys, I did a quick PoC on a small project. It parallelize the mojo per phase with a config taken from project properties - not sexy but enables to start "seeing" something. You can find it at https://github.com/rmannibucau/parallel-mojo-extension The main issue it enounters is the fact it can

Re: parallelise not overlapping tasks

Using the scm is not enough or it is for single module projects. You have to have a graph of dependencies (inputs/outputs) and save each task state in target to have incremental support But please note incremental build is != parallel build at mojo level. This last one is easy to do and a quick

Re: parallelise not overlapping tasks

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

Re: parallelise not overlapping tasks

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

Re: parallelise not overlapping tasks

Ok, my bad, thanks for the hint.

Re: parallelise not overlapping tasks

Mojos already have the ability to say if they are threadsafe, what do you see missing? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: parallelise not overlapping tasks

I think there is a difference between scheduling tasks (one is after the other) and assuming that 2 tasks that are ready can run in parallel. Adding scheduling data would be helpful and get rid of the concept of phases, for sure; but we also -and more importantly- need the existing mojos to be audi

Re: parallelise not overlapping tasks

Currently maven can't but I expect a way to do it, either in the next xsd as originally proposed or, why not, with a naming convention in the id of the execution (my-exec#after#other-exec or something like that if we want it before maven 4) The nice thing is that once done it makes phases pretty m

Re: parallelise not overlapping tasks

Hi, > any way we move that topic forward beginning of next year? I guess providing patches would be the best way ;) I'm coming late in this discussion and I'm a newcomer on that list, so I could miss context. This could relate to an effort we are doing in Eclipse IDE (and Eclipse m2e) to run mod

Re: parallelise not overlapping tasks

Hey guys, any way we move that topic forward beginning of next year? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: parallelise not overlapping tasks

I am facing very slow Maven reporting/site. I have optimized JavaDoc and avoided the javadoc plugin downloading sources, Java API which has improved the performance but still Site takes 8 minutes at least to complete. It would be worth to mark some reporting plugins running in parallel in aggregato

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