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
OSGi duplicate package export: sdk-core vs. sdk-server #59
Comments
I don't know enough about OSGi to know what the correct fix is. Can you try removing it from the sdk-server project and see if everything still works for you? |
I also just looked a bit into it. It seems that milo does also import "sun.misc", although that seems never to be used? Or did I just miss it? |
I don't see "sun.misc" used anywhere either. I suspect it was once used for something like generating certificates, but I don't see it appearing anywhere now... |
Ok ... there also is But I do spot a reference to The other two could be removed?! |
I made a PR #60 for the two packages. |
- Remove "sun.misc" and "sun.nio.ch" from the list of imported packages. - Add a Travis CI file - Use the maven-bundle-plugin in order to create OSGi metadata. It falls back to the default configuration, only overriding this when really necessary. - Prevent the maven-bundle-plugin from importing 'javax.annotation' in order to prevent a "uses violation". Signed-off-by: Jens Reimann <jreimann@redhat.com>
@JulianSchuette this should be fixed in master now... if you have a chance give it a try and let us know. |
@JulianSchuette I also did update the camel Milo repository. The layout is a bit different now, but you can create a Karat feature and archive now. Just do a local build of Milo first. |
Thank you guys! I can install and run the Would it be possible to move classes in Camel route using milo:
CNFException:
Package
|
@JulianSchuette You are always one step ahead of what I am trying to do 😉 I will look into this. But I fully agree. Different artifacts should not export different bundles. |
I am going to track this in a separate issue. |
- Remove "sun.misc" and "sun.nio.ch" from the list of imported packages. - Add a Travis CI file - Use the maven-bundle-plugin in order to create OSGi metadata. It falls back to the default configuration, only overriding this when really necessary. - Prevent the maven-bundle-plugin from importing 'javax.annotation' in order to prevent a "uses violation". Signed-off-by: Jens Reimann <jreimann@redhat.com>
Hello!
Both bundles sdk-server and sdk-core have
Export-Package: ... org.eclipse.milo.opcua.sdk.core, ...
in their OSGi headers, which leads to the following error when starting sdk-server in Karaf/Felix:
Looks like either that package import should be removed from sdk-server or sdk-server should be declared as a fragment bundle of sdk-core?
The text was updated successfully, but these errors were encountered: