Skip to content

Separation of concerns for bnd-*-maven-plugin implementations #19

Description

@timothyjward

As described in #3

If we are moving to Maven 4 (which is a good idea) then it will be a good opportunity to make breaking changes. We should consider rationalising the functionalities of the various bnd maven plugins.
For example, is it a good separation of concerns to have the testing plugin and the export plugin and the run plugin duplicate the role of the resolver plugin? If it is then we should have a contract that requires them to all operate the same way. If it isn't then we should remove the duplicate functions and make the plugins more cohesive.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions