Consider prefixing Java module names with io.github.openfeign
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.8k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 41
Description
v12.2 just added explicit Java module names to several Maven modules. The chosen module names match the automatically computed name based on their filename that is, feing-core-12.2.jar became feign.core. This ensures compatibility with anyone using computed names.
It might be better to pick a name that conveys the Feign namespace such as io.github.openfeign.* (see https://github.com/jodastephen/jpms-module-names). This is a BREAKING CHANGE and thus should only be considered when a new major release (at this point it would be 13) is in the roadmap.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the explicit Java module names in the Maven modules introduced in v12.2 and review the jpms-module-names reference linked in the issue. Confirm whether a major release 13 is planned and identify all affected module names. Done means a scoped decision on adopting the io.github.openfeign.* namespace, including the breaking-change impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100