You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Achim Nierbeck (JIRA)" <ji...@apache.org> on 2010/07/23 12:49:50 UTC
[jira] Created: (KARAF-138) WarDeploymentListener: checks for
manifest osgi entries but fails if no manifest is found
WarDeploymentListener: checks for manifest osgi entries but fails if no manifest is found
-----------------------------------------------------------------------------------------
Key: KARAF-138
URL: https://issues.apache.org/jira/browse/KARAF-138
Project: Karaf
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Achim Nierbeck
The war-deployer checks for a manifest entry of the war bundle to see if it is a OSGi web-app, but if the war doesn't contain a manifest, it fails. This shouldn't happen since a non-osgi war could be without a Manifest.
unfortunately I didn't see this error before 2.0 :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (KARAF-138) WarDeploymentListener: checks for
manifest osgi entries but fails if no manifest is found
Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Achim Nierbeck updated KARAF-138:
---------------------------------
Attachment: org.apache.karaf.deployer.war.patch
The required patch to fix this bug
> WarDeploymentListener: checks for manifest osgi entries but fails if no manifest is found
> -----------------------------------------------------------------------------------------
>
> Key: KARAF-138
> URL: https://issues.apache.org/jira/browse/KARAF-138
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Achim Nierbeck
> Attachments: org.apache.karaf.deployer.war.patch
>
>
> The war-deployer checks for a manifest entry of the war bundle to see if it is a OSGi web-app, but if the war doesn't contain a manifest, it fails. This shouldn't happen since a non-osgi war could be without a Manifest.
> unfortunately I didn't see this error before 2.0 :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (KARAF-138) WarDeploymentListener: checks for
manifest osgi entries but fails if no manifest is found
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved KARAF-138.
-----------------------------------
Assignee: Guillaume Nodet
Fix Version/s: 2.2.0
Resolution: Fixed
Committing to https://svn.apache.org/repos/asf/karaf/trunk ...
M deployer/war/src/main/java/org/apache/karaf/deployer/war/WarDeploymentListener.java
Committed r985825
Thx a lot for this patch.
> WarDeploymentListener: checks for manifest osgi entries but fails if no manifest is found
> -----------------------------------------------------------------------------------------
>
> Key: KARAF-138
> URL: https://issues.apache.org/jira/browse/KARAF-138
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Achim Nierbeck
> Assignee: Guillaume Nodet
> Fix For: 2.2.0
>
> Attachments: org.apache.karaf.deployer.war.patch
>
>
> The war-deployer checks for a manifest entry of the war bundle to see if it is a OSGi web-app, but if the war doesn't contain a manifest, it fails. This shouldn't happen since a non-osgi war could be without a Manifest.
> unfortunately I didn't see this error before 2.0 :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.