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

Java Imports & Empty header #5588

Merged
merged 1 commit into from
Mar 10, 2023

Conversation

pkriens
Copy link
Member

@pkriens pkriens commented Mar 10, 2023

  • The java imports are now always done except when the used framework is < 1.9 (before R7). The EE version is now ignored.
  • The version used to come from the imports. However, that does not make sense, so I've changed it to the classpathExports version of the framework package. This is in almost all cases the floor of the import range. By using the export, we can make the decision that we use an old framework in any bundle that has the framework package on the class path and not only in bundles that import the framework. (Surprised this was not a problem?)
  • The MRJ will now set the Input-Package and/or Require-Capability to an empty string since the spec is rather strange imho. The RFC is a tiny bit clearer but this case should be made more explicit.

This fixes #5585

The PR #5581 can now be tried again after this is merged


Signed-off-by: Peter Kriens Peter.Kriens@aQute.biz

- The java imports are now always done except when the used framework
  is < 1.9 (before R7). The EE version is now ignored.
- The version used to come from the _imports_. However, that does not make sense, so
  I've changed it to the classpathExports version of the framework package. This is in
  almost all cases the floor of the import range. By using the export, we can make the
  decision that we use an old framework in any bundle that has the framework package
  on the class path and not only in bundles that import the framework. (Surprised this
  was not a problem?)
- The MRJ will now set the Input-Package to Require-Capability to an empty string
  since the spec is rather strange imho. The RFC is a tiny bit clearer but this
  case should be made more explicit.

---
 Signed-off-by: Peter Kriens <Peter.Kriens@aQute.biz>

Signed-off-by: Peter Kriens <Peter.Kriens@aQute.biz>
@pkriens pkriens merged commit c6c7f37 into master Mar 10, 2023
@pkriens pkriens deleted the issue/java_imports_and_empty_header_in_mrj branch March 10, 2023 17:46
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 this pull request may close these issues.

Package imports for java.* & compatibility
1 participant