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

Package Import / Export analyser does not fail if an internal bundle is included and accesses internal API #231

Closed
cziegeler opened this issue Jul 25, 2024 · 1 comment · Fixed by #244
Assignees

Comments

@cziegeler
Copy link
Contributor

If a bundle is included which is the same as a bundle we have in the internal region, then the user bundle is currently granted access to the internal API; I assume it is treated like the internal bundle
For example including com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:2.17.1 does not result in an error, although it is accessing snakeyaml which is not public api

@cziegeler
Copy link
Contributor Author

The features are aggregated with the "ALL" merging rule, meaning that if the same artifact is in the source and the target feature than both end up in the target. However, if the artifacts are identical (same version as well), then this gets merged into a single artifact (which makes sense in the general case)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant