Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up package structure to avoid split package usage #883

Closed
Tracked by #860
nscuro opened this issue Oct 26, 2023 · 0 comments · Fixed by #998
Closed
Tracked by #860

Clean up package structure to avoid split package usage #883

nscuro opened this issue Oct 26, 2023 · 0 comments · Fixed by #998
Assignees
Labels
p3 Nice-to-have features size/S Small effort technical debt
Milestone

Comments

@nscuro
Copy link
Member

nscuro commented Oct 26, 2023

We currently have multiple modules that have classes in the org.hyades package. Quarkus is warning about this being bad practice on every startup:

Detected a split package usage which is considered a bad practice and should be avoided. Following packages were detected in multiple archives: 
- "org.hyades.config" found in [org.hyades:commons::jar, org.hyades:vulnerability-analyzer::jar]

Classes should be moved to more dedicated packages such that no two modules share the exact same package.

@nscuro nscuro added technical debt p3 Nice-to-have features size/S Small effort labels Oct 26, 2023
@nscuro nscuro mentioned this issue Oct 26, 2023
34 tasks
@nscuro nscuro added this to the 0.3.0 milestone Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p3 Nice-to-have features size/S Small effort technical debt
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants