[
https://issues.apache.org/jira/browse/FELIX-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Estermann updated FELIX-6060:
------------------------------------
Description:
*My use-case:*
I have a Maven POM with the Maven Bundle Plugin, which builds two bundles. I
order to do that, I specified two executions, one of which overwrites the
default execution with the ID default-bundle and the other one for creating an
additional artifact with a special classifier. My runtime environment requires
that the bundle with a classifier doesn't contain maven directory inside of
META-INF.
*The suggested solution:*
Since the Maven Bundle Plugin
[supports|http://felix.apache.org/documentation/faqs/apache-felix-bundle-plugin-faq.html#how-do-i-remove-the-generated-maven-information-from-the-resulting-bundle-jar-file]
{{addMavenDescriptor}} option for the built archive, I set it to {{false}} for
the additional execution of the Maven Bundle Plugin.
*Expected outcome:*
The main bundle still contains {{META-INF/maven}}, but the additional one
doesn't.
*The result:*
The option {{addMavenDescriptior}} seems to be ignored so that both bundles
contain {{META-INF/maven}} folder. If I set that option for the plugin
globally, i.e. in the configuration outside of the execution list, it works
then, but none of the resulting bundles contain {{META-INF/maven}}.
*Simple example:*
A simple POM for reproducing this issue can be found on
[github|https://github.com/Smasherr/mbp-amd-test]
was:
*My use-case:*
I have a Maven POM with the Maven Bundle Plugin, which builds two bundles. I
order to do that, I specified two executions, one of which overwrites the
default execution with the ID default-bundle and the other one for creating an
additional artifact with a special classifier. My runtime environment requires
that the bundle with a classifier doesn't contain maven directory inside of
META-INF.
*The suggested solution:*
Since the Maven Bundle Plugin
[supports|http://felix.apache.org/documentation/faqs/apache-felix-bundle-plugin-faq.html#how-do-i-remove-the-generated-maven-information-from-the-resulting-bundle-jar-file]
{{addMavenDescriptor}} option for the built archive, I set it to {{false}} for
the additional execution of the Maven Bundle Plugin.
*Expected outcome:*
The main bundle still contains {{META-INF/maven}}, but the additional one
doesn't.
*The result:*
The option {{addMavenDescriptior}} seems to be ignored so that both bundles
contain {{META-INF/maven}} folder. If I set that option for the plugin
globally, i.e. in the configuration outside of the execution list, it works
then, but none of the resulting bundles contain {{META-INF/maven}}.
*Simple example:*
A simple POM for reproducing this issue can be found on
[github|https://github.com/Smasherr/mbp-amd-test]
> addMavenDescriptor doesn't work on the execution level
> ------------------------------------------------------
>
> Key: FELIX-6060
> URL: https://issues.apache.org/jira/browse/FELIX-6060
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-4.1.0
> Reporter: Daniel Estermann
> Priority: Minor
>
> *My use-case:*
> I have a Maven POM with the Maven Bundle Plugin, which builds two bundles. I
> order to do that, I specified two executions, one of which overwrites the
> default execution with the ID default-bundle and the other one for creating
> an additional artifact with a special classifier. My runtime environment
> requires that the bundle with a classifier doesn't contain maven directory
> inside of META-INF.
> *The suggested solution:*
> Since the Maven Bundle Plugin
> [supports|http://felix.apache.org/documentation/faqs/apache-felix-bundle-plugin-faq.html#how-do-i-remove-the-generated-maven-information-from-the-resulting-bundle-jar-file]
> {{addMavenDescriptor}} option for the built archive, I set it to {{false}}
> for the additional execution of the Maven Bundle Plugin.
> *Expected outcome:*
> The main bundle still contains {{META-INF/maven}}, but the additional one
> doesn't.
> *The result:*
> The option {{addMavenDescriptior}} seems to be ignored so that both bundles
> contain {{META-INF/maven}} folder. If I set that option for the plugin
> globally, i.e. in the configuration outside of the execution list, it works
> then, but none of the resulting bundles contain {{META-INF/maven}}.
> *Simple example:*
> A simple POM for reproducing this issue can be found on
> [github|https://github.com/Smasherr/mbp-amd-test]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
