You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Tomas Forsman (JIRA)" <ji...@apache.org> on 2012/05/25 16:30:23 UTC
[jira] [Created] (AXIOM-424) axiom bundles does not have
MANIFEST.MF as first entry of the zip
Tomas Forsman created AXIOM-424:
-----------------------------------
Summary: axiom bundles does not have MANIFEST.MF as first entry of the zip
Key: AXIOM-424
URL: https://issues.apache.org/jira/browse/AXIOM-424
Project: Axiom
Issue Type: Bug
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>mvn:org.apache.ws.commons.axiom/axiom-api/1.2.13</bundle>
<bundle>mvn:org.apache.ws.commons.axiom/axiom-dom/1.2.13</bundle>
<bundle>mvn:org.apache.ws.commons.axiom/axiom-impl/1.2.13</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 mvn:org.apache.ws.commons.axiom/axiom-impl/1.2.13"
OpenJPA had the same issue and has solved it: https://issues.apache.org/jira/browse/OPENJPA-1737
"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." -- http://mail-archives.apache.org/mod_mbox/karaf-user/201106.mbox/%3CBANLkTim7gVYOWqwaZRYUFOOHcJ0La2Y8iA@mail.gmail.com%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
[jira] [Updated] (AXIOM-424) axiom bundles does not have
MANIFEST.MF as first entry of the zip
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIOM-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIOM-424:
----------------------------------
Component/s: LLOM
DOOM
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: https://issues.apache.org/jira/browse/AXIOM-424
> 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>mvn:org.apache.ws.commons.axiom/axiom-api/1.2.13</bundle>
> <bundle>mvn:org.apache.ws.commons.axiom/axiom-dom/1.2.13</bundle>
> <bundle>mvn:org.apache.ws.commons.axiom/axiom-impl/1.2.13</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 mvn:org.apache.ws.commons.axiom/axiom-impl/1.2.13"
> OpenJPA had the same issue and has solved it: https://issues.apache.org/jira/browse/OPENJPA-1737
> "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." -- http://mail-archives.apache.org/mod_mbox/karaf-user/201106.mbox/%3CBANLkTim7gVYOWqwaZRYUFOOHcJ0La2Y8iA@mail.gmail.com%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org