[
https://issues.apache.org/jira/browse/FELIX-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch updated FELIX-3349:
------------------------------------
Fix Version/s: maven-bundle-plugin-2.4.0
> wrong bundle manifest contents in some cases
> --------------------------------------------
>
> Key: FELIX-3349
> URL: https://issues.apache.org/jira/browse/FELIX-3349
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.6
> Reporter: Igor Fedorenko
> Fix For: maven-bundle-plugin-2.4.0
>
> Attachments: mbp-wrong-bsn.zip
>
>
> When maven-jar-plugin configuration uses relative manifestFile path (i.e.
> <manifestFile>META-INF/MANIFEST.MF</manifestFile>),
> org.apache.felix.bundleplugin.JarPluginConfiguration will calculate
> manifestFile relative to JVM current working directory instead of
> ${project.basedir}. This can result in unexpected/wrong generated bundle
> manifest contents for multi-module projects. I'll attach an example project
> that demonstrates the problem shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
