← Back to issue list

maven-use plugin: Support `disable-parallel` parameter

View original Github issue

Metadata

Project
craft-parts
Number
#1244
Type
issue
State
open
Author
lengau
Labels
Type: Enhancement Status: Needs information
Created
Updated
Closed
—

Current evaluation

Maintainer-filed request to add the disable-parallel part property to the maven-use plugin. Marked Enhancement/Needs information; maintainer states it is extremely low priority pending a real-world use case, none supplied in ~395 days.

Suggested action: keep open

Reason: The issue is valid, maintainer-authored, explicitly triaged and labelled (Type: Enhancement, Status: Needs information), with a stated implementation path ('All of our plugins should theoretically support this'), so it should stay open — its age and low priority are not grounds for closure. I confirmed at HEAD that MavenUsePluginProperties (craft_parts/plugins/maven_use_plugin.py:35) has no disable_parallel field while the autotools plugin already has the reference pattern (autotools_plugin.py:49 and :133, `make` vs `make -j{parallel_build_count}`), so the change is cheap. Impact and actionability are dampened because the maven-use plugin never passes any parallel flag to `mvn deploy` today, meaning the property would currently be a no-op absent a design decision on Maven's `-T`, and the maintainer's requested real-world use case ('this application simply does not build with parallel') has not been provided in 395 days across ~15 sibling issues.

Evaluated by: mr-cal-bot

Impact: 22 Quick Win: 7 Complexity: 30 Confidence: 80 Actionability: 48

Issue body

### What needs to get done Support the [disable-parallel](https://canonical-craft-parts.readthedocs-hosted.com/latest/common/craft-parts/reference/part_properties/#disable-parallel) part property in the maven-use plugin. ### Why it needs to get done All of our plugins should theoretically support this. In practice though, this is extremely low priority until someone shows us a real-world use case for it. If someone can bring us a real-world use case that we can test against (especially a case of "this application simply does not build with parallel"), that would be ideal. The [autotools plugin](https://github.com/canonical/craft-parts/pull/1167) required this for OpenJDK builds, for example.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 22
Quick Win: 7
Complexity: 30
Confidence: 80
Actionability: 48
keep open Maintainer-filed request to add the disable-parallel part property to the maven-use plugin. Marked Enhancement/Needs information; maintainer states it is extremely low priority pending a real-world use case, none supplied in ~395 days.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 13
Complexity: 30
Confidence: 70
Actionability: 60
keep open Request to add `disable-parallel` part property to the maven-use plugin. Open 384 days with no real-world use case provided; marked low priority.
qwen/qwen3.8-27b
Impact: 15
Quick Win: 12
Staleness: 82
Complexity: 20
Confidence: 80
Support Request: 5
close stale Feature request to add the disable-parallel part property to the maven-use plugin. Labeled 'Needs information' by the maintainer, who asked for a real-world use case; no comments or use case provided in 12 months.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 40
Confidence: 85
Support Request: 10
close stale Request to add disable-parallel parameter support to the maven-use plugin. Currently pending a real-world use case for testing, with no maintainer engagement or comments in over 322 days.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 25
Confidence: 85
Support Request: 10
close stale Enhancement to add disable-parallel support to the maven-use plugin. Labeled needs information with no maintainer comments or activity in nearly 10 months, awaiting a real-world use case.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/craft-parts#1243 (confidence 95%)

    Sibling 'maven plugin: Support disable-parallel parameter' issue, same scope against MavenPluginProperties; fixing one should fix the other.

  • Related To: canonical/craft-parts#1167 (confidence 90%)

    Autotools plugin PR cited in the issue body as the precedent implementation (required for OpenJDK builds) and the pattern to copy.

  • Related To: canonical/craft-parts#1234 (confidence 85%)

    cmake plugin disable-parallel issue, also open with parallel_build_count usage at cmake_plugin.py:136; part of the same maintainer-filed batch.

Related issues

Issue Project State Summary Similarity
#1243 maven plugin: Support `disable-parallel` parameter craft-parts open Maven plugin support for disable-parallel remains unimplemented; the open enhancement is maintainer-marked Needs information and deliberately low priority pending a real-world failing build.
92%
#1245 meson plugin: Support `disable-parallel` parameter craft-parts open Enhancement request to add `disable-parallel` support to the meson plugin. Open, labelled Enhancement/Needs information by maintainer lengau; explicitly deprioritized until someone provides a real-world use case to test against.
81%
#1249 qmake plugin: Support `disable-parallel` parameter craft-parts open Enhancement: add disable-parallel support to the qmake plugin. Maintainer-filed, labeled Needs information; explicitly deferred as low priority pending a real-world use case. One of six sibling per-plugin issues (cmake, meson, make, go, rust).
79%
#1239 gradle plugin: Support `disable-parallel` parameter craft-parts open Feature request: add `disable-parallel` support to the gradle plugin. Maintainer labels it low-priority, 'Needs information', asking for a real-world use case that fails under parallel builds; design (None/False/True) sketched in a comment.
78%
#1242 make plugin: Support `disable-parallel` parameter craft-parts open Enhancement: make plugin should honor the disable-parallel part property (currently always emits make -j"N"). Filed by a maintainer, labeled Triaged/Enhancement, and explicitly deferred as "extremely low priority" until a real-world non-parallel-build use case is supplied; autotools already has it via PR #1167.
78%
#1235 dotnet plugin: Support `disable-parallel` parameter craft-parts open Maintainer-filed enhancement: dotnet plugin does not honor the existing `disable-parallel` part property. Labeled Needs information and explicitly deferred as "extremely low priority" pending a real-world use case; no comments in 395 days.
77%
#1232 ant plugin: Support `disable-parallel` parameter craft-parts open Ant plugin support for disable-parallel is unimplemented; the request remains open as Needs information, with maintainers requesting a real-world case that fails under parallel builds.
77%
#1234 cmake plugin: Support `disable-parallel` parameter craft-parts open Enhancement: make the cmake plugin honour the `disable-parallel` part property. Still unimplemented at HEAD (cmake_plugin.py always emits `-j{parallel_build_count}`). Maintainer-filed, labelled Enhancement/Needs information; explicitly deprioritised pending a real-world use case.
77%
#1240 java plugin: Support `disable-parallel` parameter craft-parts open Java base disable-parallel support remains open and Needs information: the property is not implemented, and no real-world Java build failing under parallelism has been supplied.
77%
#1241 jlink plugin: Support `disable-parallel` parameter craft-parts open Maintainer-filed, triaged enhancement to honour the disable-parallel part property in the jlink plugin. Labeled Needs information; jlink never uses parallel_build_count, so the property would likely be a no-op. Open 395 days, no comments.
76%