spring-cloud / spring-cloud/spring-cloud-commons
Please provide automatic module-name(s) (Add "Automatic-Module-Name"-Entry to Manifest(s))
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 751
- Forks
- 744
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 9
Description
Using spring-cloud-context in a project where I add a module-descriptor (module-info.java) I get the following warning during the build:
[WARNING] ******************************************************************************************************************************************************
[WARNING] * Required filename-based automodules detected: [spring-cloud-context-4.2.0.jar]. Please don't publish this project to a public artifact repository! *
[WARNING] ******************************************************************************************************************************************************
I examined the reason: the jar does not provide a reliable module-name in its Manifest.
Please add module name(s).
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 spring-cloud-context-4.2.0.jar manifest and the repository build configuration that creates it. Identify the affected published JAR manifests and define reliable Automatic-Module-Name entries for them. Done means the build no longer reports required filename-based automodules for the affected artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100