ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Updated] (AXIOM-424) axiom bundles does not have MANIFEST.MF as first entry of the zip
Date Fri, 25 May 2012 22:26:23 GMT


Andreas Veithen updated AXIOM-424:

    Component/s: LLOM

The issue occurs with bundles that are post-processed using the maven-shade-plugin. For Axiom
this is the case with axiom-impl and axiom-dom. This was also the root cause of the issue
with OpenJPA.

I don't see a quick workaround for this. The proper solution would be to fix maven-shade-plugin
such that it always adds the manifest first, but I would have to check if that can be done
without too much changes.
> axiom bundles does not have MANIFEST.MF as first entry of the zip
> -----------------------------------------------------------------
>                 Key: AXIOM-424
>                 URL:
>             Project: Axiom
>          Issue Type: Bug
>          Components: DOOM, LLOM
>    Affects Versions: 1.2.13
>         Environment: Karaf 2.2.6
>            Reporter: Tomas Forsman
> The problem occurs when trying to install axiom-impl (or axiom-dom) from within a karaf-feature
> <feature name="axiom-test" version="1.0.0-SNAPSHOT">
>         <!-- possible that other bundles are needed here, this is just an example
>         <bundle></bundle>
>         <bundle></bundle>
>         <bundle></bundle>
> </feature>
> Typeing "feature:install axiom-test" from within karaf will give the following error:
> "Error executing command: Manifest not present in the first entry of the zip"
> OpenJPA had the same issue and has solved it:
> "This issue only shows up when you do a features:install because the
> features service is looking at the MANIFEST.MF right upfront to
> determine if it needs to install the bundle or if there's already a
> suitable bundle available in the container." --

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message