mvnd ignores -b (--builder) and -T (--threads) parameter
- Dominant language
- Java
- Stars
- 3.5k
- Forks
- 250
- Avg merge
- 16h 22m
- Merged PRs (30d)
- 36
Description
### Affected version
1.0.3
### Bug description
Maven Daemon prefers Takari smart builder by default.
The problem is that it ignores explicitly configured builder on the command line or in the `.mvn/maven.config`.
E.g. it's not possible to use https://github.com/maven-turbo-reactor/maven-turbo-builder adding it to `.mvn/extensions.xml` in combination with neither CLI `-b turbo` nor `.mvn/maven.config` `-bturbo`.
According to ` mvnd -h | grep builder` there are two ways for it:
```
-b,--builder The id of the build strategy to use
-Dmvnd.builder=;-b,--builder The builder implementation the daemon should use.
takari-smart-builder extension, remain buildable with mvnd (where use of this extension would cause issues). Value is expected as comma separated pairs.
Default: io.takari.maven:takari-smart-builder
```
The second `-Dmvnd.builder=turbo` works fine.
Same problem with `-T` (`--threads`) which is always defined as default `-T1C` (`-Dmvnd.threads=6` works fine). But the `mvnd -h` claims both should be supported
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the reported behavior with mvnd 1.0.3 using -b/--builder and -T/--threads, both on the command line and through .mvn/maven.config, then compare it with the working -Dmvnd.builder and -Dmvnd.threads forms. Trace the argument handling and verify that the documented options select the requested builder and thread count without relying on the system defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100