-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
Better explain the implications of -nouses instruction #6439
Comments
Any suggestion on what to write there? I had a look and found 2 places where this is used:
|
The spec might be a good first source for derive some normative things:
The most important part is this one here
So I hardly can imagine why one would want to disable this at all (and it seems only be either on or off...).
This is where the flag is evaluated (I hope bnd nowhere uses the flag to disable this). |
Docu change is live https://bnd.bndtools.org/instructions/nouses.html |
Because of issue
I further analyzed the problem and found it to be a missing use clause:
i then tried to fix the project (what uses maven-bundle plugin / bnd already!) but without success. It took me some time to realize, that with this commit all Apache commons projects effectively disable use clauses on their export package instructions.
The commit do not mentioned any rationale and I thought it would be good to make the project aware of the issue by linking the documentation that will obviously war that this is dangerous and maybe list cases where it should or should not be used but:
https://bnd.bndtools.org/instructions/nouses.html
only tells
I find disabling this extremely dangerous and the doc should at least mention the implications of not using uses directives on packages (and capabilities)
The text was updated successfully, but these errors were encountered: