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.

Sign up for GitHub

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

Jump to bottom

Improve separation of concerns #44

Open

valeriopilo-tomtom opened this issue May 30, 2022 · 0 comments

Labels

valeriopilo-tomtom commented May 30, 2022 •

edited

Loading

Corporate users of this library have the issue of independently obtaining different tools located inside of one repository.

All individual tools should be fully separated to different Gradle artifacts with independent version numbering.

Reasons are:

Artifact names need to be straight to the point.
Versioning each module separately makes tracking changes easier.
Users get exclusively the necessary functionality.
Corporate dependency addition review processes is made simpler: currently a version change due to e.g. memoization causes a new version to be available for trace-events, which has no actual changes, and is unwanted.

rijnb added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment