They *should* be parallelizable, as Maven takes the dependency graph computed by the reactor, to set which modules can be build in parallel [1]. Anyway, the feature is experimental, and they already say there might be still some undiscovered issues, so I'm not sure if we can rely on it yet.
I'm ok reverting the change, although it would be good to see if we can determine why those weird compilation error occur, as in theory, they shouldn't appear. Perhaps could be good to have a new build to play with this? I. [1] https://cwiki.apache.org/confluence/display/MAVEN/Parallel+builds+in+Maven+3 On 3 May 2014 02:55, Andrew Phillips <andr...@apache.org> wrote: >> Added "-T 2C" to "jclouds-pull-requests" but *not* to >> "jclouds-java-7-pull-requests", so we should be able to see what (if >> any) the difference is. > > > I'm afraid I've had to revert this change. This has been reliably > causing the jclouds-pull-request job [1] to fail with weird > compilation errors in dynect where the jclouds-java-7-pull-request job > (which didn't have this change) was fine [2]. > > Looks like our builds are not parallelizable? Or, at any rate, not on > DEV@cloud? Any other settings/different values for the settings we > could try? > > ap > > [1] > https://jclouds.ci.cloudbees.com/view/pull%20requests/job/jclouds-pull-requests/780/console > [2] > https://jclouds.ci.cloudbees.com/view/pull%20requests/job/jclouds-java-7-pull-requests/1250/console >
