playframework / playframework/play-slick
Suggest removing jdbc dependency
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 794
- Forks
- 272
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 17
Description
The standard Play template bundles the jdbc dependency. Users will usually need to remove this dependency when they add the play-slick dependency. Mention this in the docs.
Could also mention that the error A binding to play.api.db.DBApi was already configured happens when both jdbc and play-slick are on the classpath together.
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 in the play-slick documentation and find the dependency setup guidance for the standard Play template. Document that users should remove jdbc when adding play-slick, and include the DBApi binding error that occurs when both are present. Done means the dependency conflict and its resolution are clearly explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100