garydgregory commented on PR #725: URL: https://github.com/apache/commons-parent/pull/725#issuecomment-6058689194
So the cons are, for _all_ of Apache Commons: - modern OSGi users lose useful dependency metadata - we now get failures to move from OSGi failures in _resolution_ to JVM failures in _execution_, for example getting a `NoClassDefFoundError` for `java.sql` - we lose early detection of missing Java packages across Commons to accommodate an old (unsupported?) OSGi framework. Dealing with an old version of one OSGi vendor is not enough to justify the loss IMO. To be fair, the risk is likely small for "normal" JDK/JRE deployments, but still clutters things up for all of Commons. Let's see what other folks have to say either way. -- 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]
