ensure that packages are not split across jars
- Dominant language
- Scala
- Stars
- 196
- Forks
- 55
- Avg merge
- 4d 52m
- Merged PRs (30d)
- 74
Description
We have at least some packages split across pekko-http and pekko-http-core, eg
* org.apache.pekko.http.javadsl.settings
* org.apache.pekko.http.scaladsl.settings
With Java modules (JPMs), the idea is that packages are implemented in just one jar. This is a useful security feature because it stops rogue lib maintainers from sneakily adding variants of classes from other libs in their libs.
Contributor guide
Research direction
Start by inspecting how the pekko-http and pekko-http-core jars are assembled, then compare their contents for org.apache.pekko.http.javadsl.settings and org.apache.pekko.http.scaladsl.settings. Read the Java module (JPM) requirements referenced in the issue and identify the project check or packaging step that can verify package ownership. Done means no package is split across the two jars.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100