fix(maven-use): always set version
Metadata
Current evaluation
Merged a fix for the maven-use plugin that automatically assigns an available version to dependencies when unspecified, preventing errors. Approved by three reviewers and passed all CI checks across multiple Python and OS environments.
Suggested action: —
No scores available.
Issue body
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you added an entry to the changelog (`docs/reference/changelog.rst`)?
-----
The maven-use plugin will always overwrite the version number of a dependency with whatever is available (unless, of course, what's available is already being used). In the case that a version number isn't specified at all, instead of raising an error, the plugin should just simply write in a version that is available.
CRAFT-4601
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a fix for the maven-use plugin that automatically assigns an available version to dependencies when unspecified, preventing errors. Approved by three reviewers and passed all CI checks across multiple Python and OS environments. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged fix for the maven-use plugin that automatically assigns a dependency version when unspecified, preventing errors. Resolves CRAFT-4601. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1215 feat(maven-use): improve selection when rewriting version numbers | craft-parts | merged | Merged improvement to Maven version selection logic during rewrites. Approved by three reviewers and passed all CI checks. Adds full test coverage and documents edge cases across five files to handle arbitrary strings. |