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

Batik dependencies should be declared with Import-Package instead of Required-Bundle #22

Open
amergey opened this issue Oct 20, 2022 · 0 comments

Comments

@amergey
Copy link

amergey commented Oct 20, 2022

Currently Batik dependencies are declared with Required-Bundle
It would be better to use Import-Package instead as batik will be osgified (see apache/xmlgraphics-batik#30)

Currently Required-Bundle force to use Orbit Bundle and prevent using servicemix or regular batik when osgified

The reason to take regular batik instead of orbit is cleaner for build based on maven. More and more part of eclipse are deployed in maven central, and it is better to take things from maven than p2 (in order to be able to use Dependency Analysis Platform)

More than that osgi world recommends Import-Package over Required-Bundle

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

No branches or pull requests

1 participant