spring-projects / spring-projects/spring-modulith
Overide existing dependency behaviour
Open
@odrotbohm is already working on this.
Since Mar 21, 2023.
in: core
meta: waiting for feedback
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Reading the documentation it states:
an application module’s base package is considered the API package and thus is the only package to allow incoming dependencies from other modules.
However, I like to organise my packages with sub-packages instead of having all my classes in the base package; for example, if I have a common module with a lot of utility classes, I'd like the ability to organise them.
Is there a way Spring Modulith can be configured to allow the package and all of it's subpackages to be included as a dependency without having to define named interfaces for each of the subpackages?
Please let me know if this doesn't make sense :)
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.
Assessment
This issue has not been assessed yet.