cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darren Shepherd <darren.s.sheph...@gmail.com>
Subject Re: parallel mvn builds
Date Fri, 01 Nov 2013 00:00:33 GMT
I use it all the time with -T 1.5C and it makes my build twice as fast.
But I do it with the assumption that "it may void your warranty."
Sometimes things blow up, and then I go back to single threaded.  So it
kinda works, but it does blow up.

I wouldn't recommend most people use it.  For people who are closer to full
time ACS developers it can be helpful.  For people that don't use ACS much,
its not worth the hassle because its not guaranteed to work and I have seen
it fail.

Darren


On Thu, Oct 31, 2013 at 3:36 PM, John Kinsella <jlk@stratosec.co> wrote:

> I've been tinkering with adding -T to builds on my laptop - e.g. "mvn -T
> 2C install" (Means run two build threads on each CPU core the system has)
>
> I'm seeing a 20-30% improvement in build time vs a single-thread build,
> and things seem to work so far, but I do get this warning a few times
> during the build:
>
> [WARNING] *****************************************************************
> [WARNING] * Your build is requesting parallel execution, but project      *
> [WARNING] * contains the following plugin(s) that are not marked as       *
> [WARNING] * @threadSafe to support parallel building.                     *
> [WARNING] * While this /may/ work fine, please look for plugin updates    *
> [WARNING] * and/or request plugins be made thread-safe.                   *
> [WARNING] * If reporting an issue, report it against the plugin in        *
> [WARNING] * question, not against maven-core                              *
> [WARNING] *****************************************************************
> [WARNING] The following plugins are not marked @threadSafe in Apache
> CloudStack:
> [WARNING] org.apache.maven.plugins:maven-site-plugin:3.1
> [WARNING] *****************************************************************
>
> Curious if anybody else has tried this or if we should recommend it to
> folks?
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message