[
https://issues.apache.org/jira/browse/OPENJPA-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-1737:
----------------------------------
Fix Version/s: 2.0.1
2.1.0
Component/s: build / infrastructure
osgi
Problem is related to how we're using maven-shade-plugin and
maven-bundle-plugin together. Some manifest info was being injected by the
shade plugin, which seems to mess the ordering up. Once I moved the injection
of manifest data from the shade plugin to the bundle plugin, the manifest file
is now the first file in the jar -
drwoods:openjpa/$ unzip -l target/openjpa-2.1.0-SNAPSHOT.jar
Archive: target/openjpa-2.1.0-SNAPSHOT.jar
Length Date Time Name
-------- ---- ---- ----
0 07-21-10 14:15 META-INF/
22219 07-21-10 14:15 META-INF/MANIFEST.MF
> The openjpa-2.0.0.jar does not have its MANIFEST.MF has the first entry
> -----------------------------------------------------------------------
>
> Key: OPENJPA-1737
> URL: https://issues.apache.org/jira/browse/OPENJPA-1737
> Project: OpenJPA
> Issue Type: Bug
> Components: build / infrastructure, osgi
> Affects Versions: 2.0.0
> Reporter: Guillaume Nodet
> Assignee: Donald Woods
> Fix For: 2.0.1, 2.1.0
>
>
> This is a requirement for valid jars and it causes some problems for tools
> that expect the manifest as the first entry.
> Karaf does that in some places so that it can read the manifest from a remote
> location without having to download the full jar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
