From dev-return-17942-apmail-ws-dev-archive=ws.apache.org@ws.apache.org Mon May 22 14:35:10 2017 Return-Path: X-Original-To: apmail-ws-dev-archive@www.apache.org Delivered-To: apmail-ws-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2864D19706 for ; Mon, 22 May 2017 14:35:10 +0000 (UTC) Received: (qmail 56432 invoked by uid 500); 22 May 2017 14:35:09 -0000 Delivered-To: apmail-ws-dev-archive@ws.apache.org Received: (qmail 56047 invoked by uid 500); 22 May 2017 14:35:09 -0000 Mailing-List: contact dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ws.apache.org Delivered-To: mailing list dev@ws.apache.org Received: (qmail 56008 invoked by uid 99); 22 May 2017 14:35:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 May 2017 14:35:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 92013190D3C for ; Mon, 22 May 2017 14:35:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id pRTcx0U02Nso for ; Mon, 22 May 2017 14:35:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id D7A5060DFF for ; Mon, 22 May 2017 14:35:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 1D05BE0C0F for ; Mon, 22 May 2017 14:35:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 616FD21B5A for ; Mon, 22 May 2017 14:35:04 +0000 (UTC) Date: Mon, 22 May 2017 14:35:04 +0000 (UTC) From: "Hudson (JIRA)" To: dev@ws.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AXIOM-424) axiom bundles does not have MANIFEST.MF as first entry of the zip MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AXIOM-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019635#comment-16019635 ] Hudson commented on AXIOM-424: ------------------------------ SUCCESS: Integrated in Jenkins build axiom-trunk #2853 (See [https://builds.apache.org/job/axiom-trunk/2853/]) Use maven-bundle-plugin instead of maven-shade-plugin to include aspects and components into OSGi bundles. This should also solve AXIOM-424. (veithen: rev 1795801) * (edit) axiom/aspects/core-aspects/pom.xml * (edit) axiom/aspects/dom-aspects/pom.xml * (edit) axiom/aspects/fom-aspects/pom.xml * (edit) axiom/aspects/om-aspects/pom.xml * (edit) axiom/aspects/pom.xml * (edit) axiom/aspects/shared-aspects/pom.xml * (edit) axiom/axiom-api/pom.xml * (edit) axiom/buildutils/pom.xml * (delete) axiom/buildutils/shade-osgi * (edit) axiom/components/base64-utils/pom.xml * (edit) axiom/components/core-streams/pom.xml * (edit) axiom/components/pom.xml * (edit) axiom/components/xml-utils/pom.xml * (edit) axiom/implementations/axiom-dom/pom.xml * (edit) axiom/implementations/axiom-impl/pom.xml * (edit) axiom/implementations/fom-impl/pom.xml * (edit) axiom/implementations/pom.xml * (edit) axiom/pom.xml > 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 > > > mvn:org.apache.ws.commons.axiom/axiom-api/1.2.13 > mvn:org.apache.ws.commons.axiom/axiom-dom/1.2.13 > mvn:org.apache.ws.commons.axiom/axiom-impl/1.2.13 > > 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 was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org For additional commands, e-mail: dev-help@ws.apache.org