![]() ![]() If we added a JAXB module to Java, we would end up with problems that classes/packages are available in two modules (the unnamed one from the OSGi bundle, and the JAXB that we added via command line). The first solution does not work well for us, because our own bundles already use an Import-Package header in the manifest to make use of JAXB which is available in our target platform as an OSGi bundle. My research so far has ended up in two possibilities to solve this:Īdd JAXB to the Java Classpath by providing it as a module and add a corresponding -add-modules argument as VM argument in the eclipse.ini.įor each legacy bundle, create a fragment with additional Import-Package headers to add the JAXB import to each of the affected bundles. When executed in our new Java 11 product, of course, this ends up in NoClassDefFoundExceptions for the JAXB classes. ![]() Now the problem is that those bundles assume that is on the (Java Runtime Library) classpath (which was correct for Java 8), so they don't have an Import-Package for JAXB in their manifests. Those bundles have been built and are working under Java 8 and use (JAXB) and we don't have access to the source code, so we cannot rebuild them for Java 11. ![]() We are trying to migrate an existing Eclipse IDE Product from Java 8 to Java 11.Įverything worked fine with our own code but, unfortunately, the product also includes some (quite old) bundles from a third party. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |