[
https://issues.apache.org/jira/browse/FELIX-6676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated FELIX-6676:
-----------------------------------
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.
was:
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.
I can accept also workaround, but for me looks like a bug.
Sample project to reproduce the problem is attached.
> Felix bundle plugin: Embed-Dependency with activator class always generates
> Bunde-Activator and Bundle-ActivationPolicy in target manifest
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-6676
> URL: https://issues.apache.org/jira/browse/FELIX-6676
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-5.1.9
> Reporter: Andrei Shakirin
> Priority: Major
> Attachments: org.apache.poi-bundle-project.zip
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
