The console output of both parallel modes is not sorted in any way, which can be a bit confusing. It is not required to report jiras for these issues:
Maven Remote Resources Plugin 1.2.1 (1.2 is not threadsafe).Plexus-utils 2.0.5 maven-archiver 2.4.1 plexus-archiver 1.0 plexus-io 1.0 Thread safe plugins and libraries Known thread safety problems have been fixed in the following library versions: EAR, EJB, JAR and WAR are fixed in latest version. All maven-archiver clients (EAR, EJB, JAR, WAR etc), see related/links section.Surefire with forkMode=never, surefire [2.6,) asserts this.As of beta-2 maven 3 will warn noisily of any plugins present in the build that are not following plugins/settings are KNOWN to have incompatibilities when running any of the parallel modes: Not all of these plugins/libraries were written with thread safety in mind. The functionality within the Maven3 core is thread safe and well behaved, but the maven ecosystem consists of a large number of subsystems, and a lot of plugins have a large number of dependencies. Remember that tcp/ip ports and files are still singletons. Running tests in parallel within a single surefire-instance is a little different from running multiple surefire-runs (from separate projects), since there will be different classloaders.Distributing tests among your modules is likely to improve performance, putting all your tests in one module decreases it - unless you run one of the parallel surefire test providers.20-50% speed improvement is quite common.This depends greatly on your module structure, but the following observations have been made: The parallel build functionality is brand new, and although they are tested with quite a few projects they do not have the general wisdom accumulated by running on multiple project types on multiple platforms within the community. We recommend that users of the parallel build feature establish their own reference as to how well this works for their project, preferably starting with everyday builds as opposed to final production releases. The parallel build feature has been subject to extensive testing, but the maven ecosystem is diverse so there will be undiscovered issues. The above mentioned thread per cpu core means the number of cores is used as a multiplier Experimental feature for 3.0! This build-mode analyzes your project's dependency graph and schedules modules that can be built in parallel according to the dependency graph of your project. Mvn -T 4 clean install # Builds with 4 threads mvn -T 1C clean install # 1 thread per cpu core mvn -T 1.5C clean install # 1.5 thread per cpu core Maven 3.x has the capability to perform parallel builds.
0 kommentar(er)
