spring-projects / spring-projects/spring-data-rest
generated POM defines dependencies with wrong scope
Open
Nobody has claimed this yet.
type: enhancement
- Dominant language
- Java
- Stars
- 958
- Forks
- 568
- PR merge metrics
- No merged PRs in 30d
Description
There are a set of dependencies that are wrong in the RC3 release for this project
- The slf4j logback should be optional or provided. We're using log4j and we had to exclude the dependency (otherwise you get two different bindings and log4j does not know which one to choose)
- hsqldb should be provided. I assume it's being used only for the sample web application
- The hibernate entity manager and validator should be optional probably
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 with the RC3 generated POM linked in the issue and identify the project entry point that produces its dependency scopes. Verify the scopes for the SLF4J/logback, HSQLDB, Hibernate entity manager, and validator dependencies; done means the generated POM marks them as optional or provided as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100