Skip to content

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

@amergey

Description

@amergey

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions