ppkarwasz commented on PR #676: URL: https://github.com/apache/commons-parent/pull/676#issuecomment-3431220607
Hi @Subrhamanya, Thanks for your contribution and for raising this! This is really a question about the **OSGi specification baseline** we want to use in Commons components. A few clarifications: * **Up to OSGi Core Release 6 (R6)**, which is the version you seem to be using, `java.*` packages could not be imported. They were assumed to be available from the bootstrap classloader. * **Since OSGi Core Release 7 (R7)**, importing `java.*` packages was explicitly allowed and recommended, especially for Java 9+ modular environments where not all `java.*` packages are guaranteed to be present by default (e.g. `java.xml`, `java.sql`, etc.). I couldn’t find any prior discussion or documentation that defines an official OSGi baseline for Apache Commons. Before we make a decision, we should bring this to the `[email protected]` mailing list so the whole community can weigh in. We essentially have two valid options: * **OSGi R6 baseline**: maximizes compatibility with very old OSGi runtimes but does not allow `java.*` imports and predates modular Java. Supporting both R6 and R7 via multi-release bundles is possible but adds unnecessary complexity. * **OSGi R7 baseline**: modern, supports `java.*` imports, works well with Java 9+, and is still compatible with **Java 8** because current Equinox and Felix versions support it. Given this, R7 seems to me like the most practical choice going forward. **TL;DR**: Could you start a discussion thread on `[email protected]` outlining why you think we should keep OSGi R6 as the baseline? You don’t have to subscribe to post, but it’s recommended so you receive replies (see mailing list info: [https://commons.apache.org/mail-lists.html](https://commons.apache.org/mail-lists.html)). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
