NetBeans Maven Build: Latency Spike When Running Concurrent Builds

Answer to the specific questions

1. Does NetBeans enforce a single‑threaded build queue? NetBeans does not enforce a single‑threaded queue for Maven builds. Each build request is submitted to the IDE’s Builder service, which uses a shared thread pool (by default sized to the number of available processors). Consequently, multiple Maven builds can run in parallel unless the pool is exhausted or explicitly limited.
2. How is Maven’s -T flag propagated? NetBeans does not automatically forward the -T parallel‑build flag to each Maven invocation. The flag must be added manually to the build command line or to the project’s Maven configuration (e.g., via MAVEN_OPTS or the properties section of the POM) for it to take effect in concurrent IDE builds.
3. Status of community discussion on a dedicated parallel‑build scheduler? There have been open tickets and forum threads requesting a NetBeans‑native parallel‑build scheduler or a configurable build queue. As of the latest NetBeans releases (14‑15), no such scheduler has been implemented; the discussion remains active in the issue tracker, with contributors suggesting that users rely on Maven’s -T flag and external resource isolation instead.

Likely explanation vs. confirmed facts

Likely explanation

When several Maven builds run concurrently from NetBeans, they share the same IDE JVM process and the underlying OS resources (CPU, disk I/O, file‑system cache). All builds also point to the same local Maven repository (~/.m2/repository) which uses file‑based locks for artifact access. Contention for these shared resources creates wait times that appear as a latency spike, especially on systems with limited cores or slow storage.

Confirmed facts

• NetBeans launches each Maven build via its embedded Maven integration, reusing the same local repository location and, when applicable, the same Maven daemon processes.
• Repository access is synchronized via file locks; concurrent builds often show messages like "Waiting for lock on local repository" in Maven debug output.
• The IDE’s Builder service uses a fixed thread pool; there is no per‑project setting to adjust this pool size from the NetBeans UI.

Steps to mitigate the latency spike (for this case)

1. Give each concurrent build its own local repository to eliminate lock contention:

   mvn clean install -Dmaven.repo.local=/path/to/unique/repo -T 4

2. Enable Maven parallel execution with the -T flag (choose a thread count appropriate to your CPU cores).
3. If lock waits remain high, increase the repository lock timeout by setting -Dmaven.repo.local on a fast SSD and/or adjusting -Dmaven.artifact.threads.
4. Limit the number of simultaneous builds in NetBeans Builder options (Tools → Options → Maven → Builder) or raise the IDE heap size (-Xms/-Xmx) to reduce GC pressure.

Missing diagnostic detail that could change the recommendation

Determine whether the concurrent builds are using the same Maven installation or different Maven versions. Version differences can affect plugin classloader isolation and locking behavior, which may require isolating not only the local repository but also the Maven home (-Dmaven.home) for each build.

Please confirm the Maven version(s) in use so we can advise whether additional isolation of the Maven installation is needed.