Uploaded image for project: 'Felix'
  1. Felix
  2. FELIX-6676

Felix bundle plugin: Embed-Dependency with activator class always generates Bunde-Activator and Bundle-ActivationPolicy in target manifest

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • maven-bundle-plugin-5.1.9
    • None
    • Maven Bundle Plugin
    • None

    Description

      Use case: I use felix bundle plugin 5.1.9 to embed third party library with transitive dependencies into my bundle with maven.

      Problem: I faced the following problem: one transitive dependency (in this case it was log4j-api-2.21.1.jar) is bundle itself and contains following entries in manifest file:
      Bundle-Activator: org.apache.logging.log4j.util.Activator
      Bundle-ActivationPolicy: lazy
      For some reason, Felix bundle plugin always sets this Bundle-Activator and Bundle-ActivationPolicy into generated manifest.
      I have no chance neither to redefine it to my activator no to remove it.

      Such behaviour looks for me like a bug.

      Sample project to reproduce the problem is attached.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            ashakirin Andrei Shakirin

            Dates

              Created:
              Updated:

              Slack

                Issue deployment