NetBeans Maven Build: Latency Spike When Running Concurrent Builds

When multiple Maven projects are built simultaneously from NetBeans, overall build time often grows disproportionately, suggesting hidden contention. The goal is to determine whether the IDE’s scheduling, Maven’s own parallel‑build flags, or shared resources (local repository, disk I/O, thread pool) are the root cause.

Key constraints include the IDE’s default task executor pool, lack of a direct setting to adjust concurrency, and the fact that Maven’s -T flag is not automatically propagated for concurrent IDE builds. The behavior varies across NetBeans releases and operating systems, making reproducibility a challenge.

Unresolved decisions in the community center on whether NetBeans should implement its own parallel‑build scheduler or enforce a single‑threaded build queue to mitigate contention.

Specific questions:

• Does NetBeans currently enforce a single‑threaded build queue for concurrent Maven builds, or does it allow parallel execution?
• How does NetBeans propagate Maven’s -T parallel‑build flag across multiple simultaneous build requests?
• What is the current status of the community discussion regarding a dedicated parallel‑build scheduler in NetBeans?