[
https://issues.apache.org/jira/browse/FELIX-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962646#comment-13962646
]
Bertrand Delacretaz commented on FELIX-4479:
--------------------------------------------
I think this is related to MIME4J-231 which has more details.
> wrong MANIFEST.MF ends up in jar bundle file sometimes
> ------------------------------------------------------
>
> Key: FELIX-4479
> URL: https://issues.apache.org/jira/browse/FELIX-4479
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.4.0
> Reporter: Mark
> Priority: Blocker
>
> Fetch the sources from
> http://svn.apache.org/repos/asf/james/server/trunk/
> and enter "mvn clean install". At the end, there will be a few karaf
> integration tests that may sometimes fail because of a Bundle-SymbolicName
> missing error. It is pretty much random and my best guess is that after the
> MANIFEST.MF modification by the plugin, the file handle is not closed
> properly, the data is not flushed to disk properly etc. because the maven
> debug output tells me that the change is recognized and the MANIFEST.MF
> included in the jar after it has been updated by maven-bundle-plugin. But
> still, the old non-OSGi version ends up in the jar file sometimes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
