apache / apache/maven-remote-resources-plugin
[MRRESOURCES-120] Inherit resourceBundle version from dependencies
- Dominant language
- Java
- Stars
- 17
- Forks
- 18
- Avg merge
- 6h 5m
- Merged PRs (30d)
- 5
Description
**[Delany](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=delany)** opened **[MRRESOURCES-120](https://issues.apache.org/jira/browse/MRRESOURCES-120?redirect=false)** and commented
The resourceBundle requires a version number when it should not.
The version number for this dependency is in the model (it was set in the dependencyManagement section of the parent). So while my dependency is
```
com.sloan:pestle
```
I am forced to include a version
```
com.sloan:pestle:4.0.4
```
instead of simply
```
com.sloan:pestle
```
For reference, other plugins like the maven-shade-plugin have no problem deriving the dependency version from the model.
---
**Affects:** 1.7.0
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the plugin resolves the resourceBundle value against the Maven project model, using the dependency and dependencyManagement examples in the issue as the expected cases. Compare that behavior with the referenced maven-shade-plugin, then verify that a resourceBundle without an explicit version inherits the managed dependency version while explicit versions continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100