ant plugin: Support `disable-parallel` parameter
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: The Status: Needs information label and explicit request for a reproducible real-world failure show that maintainers have not prioritized or fully scoped the work. Source inspection confirms that ant_plugin.py has no disable_parallel field or parallelism handling, but a practical Ant mechanism and failing project are still needed.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
30
Quick Win:
10
Complexity:
25
Confidence:
90
Actionability:
45
|
needs triage | 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. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
17
Complexity:
20
Confidence:
70
Actionability:
70
|
keep open | Add disable-parallel part property support to the ant plugin. Open 384 days with no real-world use case provided despite maintainer request. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
12
Staleness:
85
Complexity:
20
Confidence:
82
Support Request:
10
|
close stale | Feature request to add the disable-parallel part property to the ant plugin. Labeled 'Needs information' and waiting ~1 year for a real-world use case; maintainer explicitly called it extremely low priority until one is provided. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
45
Confidence:
75
Support Request:
10
|
needs triage | Feature request to add disable-parallel parameter support to the ant plugin. Currently inactive for over 10 months and awaiting a real-world use case or team prioritization. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
30
Confidence:
70
Support Request:
10
|
needs triage | Request to add disable-parallel support to the ant plugin. Labeled needs information, awaiting a real-world use case. Inactive for ~10 months with no maintainer response. |
Update history
No update history recorded yet.
Related work
-
Related To:
craft-parts#1237
(confidence 100%)
The open Go-plugin issue requests the same disable-parallel capability.
-
Related To:
craft-parts#1247
(confidence 100%)
The open Python-plugin issue requests the same capability and records unresolved control-semantics questions.
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. | |
| #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. | |
| #1237 go plugin: Support `disable-parallel` parameter | craft-parts | open | Adding disable-parallel support to the Go plugin remains open and low priority, pending a concrete real-world use case or application that fails with parallel builds. | |
| #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. | |
| #1246 npm plugin: Support `disable-parallel` parameter | craft-parts | open | Add disable-parallel support to the npm plugin. It remains open and low priority, with the maintainer requesting a real-world npm build case before prioritizing implementation. | |
| #1250 rust plugin: Support `disable-parallel` parameter | craft-parts | open | Request to honor the documented `disable-parallel` part property in the rust plugin. Maintainer-opened, labeled Needs information, explicitly deprioritized pending a real-world use case; rust_plugin.py still builds with cargo defaults. | |
| #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. | |
| #1247 python plugin: Support `disable-parallel` parameter | craft-parts | open | Python plugin support for compiled-wheel parallel control remains unimplemented; maintainers are awaiting a real-world case and resolution of tri-state semantics versus setting CRAFT_PARALLEL_BUILD_COUNT=1. | |
| #1244 maven-use plugin: Support `disable-parallel` parameter | craft-parts | 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. | |
| #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. |