Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 75812 invoked from network); 7 Jul 2008 10:00:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Jul 2008 10:00:26 -0000 Received: (qmail 66597 invoked by uid 500); 7 Jul 2008 10:00:26 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 66565 invoked by uid 500); 7 Jul 2008 10:00:26 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 66554 invoked by uid 99); 7 Jul 2008 10:00:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jul 2008 03:00:26 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jul 2008 09:59:42 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5A928234C154 for ; Mon, 7 Jul 2008 02:59:32 -0700 (PDT) Message-ID: <101212127.1215424772369.JavaMail.jira@brutus> Date: Mon, 7 Jul 2008 02:59:32 -0700 (PDT) From: "Sahoo (JIRA)" To: dev@felix.apache.org Subject: [jira] Commented: (FELIX-620) manifest goal of maven-bundle-plugin ignores _include instruction In-Reply-To: <1529737490.1215060045001.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/FELIX-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610939#action_12610939 ] Sahoo commented on FELIX-620: ----------------------------- That's good. But, as I mentioned in the README, the problem is not about missing warning. I also felt that manifest goal was not processing the instructions file. To reproduce this, please do the following (copied and pasted from the README): Just change pom.xml to use osgi.bundle and pom.xml.notworking to use osgi.bundle2. Both these files exist. Now generate two jars one with each pom.xml. Look at their manifest files. The one created with bundle goal has only sahoo.osgitest2.foo.api exported, where as the one with manifest goal exports sahoo.osgitest2.foo.impl as well as api package. So, it completely ignored the instructions found in osgi.bundle2 file. > manifest goal of maven-bundle-plugin ignores _include instruction > ----------------------------------------------------------------- > > Key: FELIX-620 > URL: https://issues.apache.org/jira/browse/FELIX-620 > Project: Felix > Issue Type: Bug > Components: Maven Bundle Plugin > Affects Versions: maven-bundle-plugin-1.4.1 > Environment: Maven version: 2.0.7 > Java version: 1.5.0_13-rev > OS name: "sunos" version: "5.11" arch: "x86" > Reporter: Sahoo > Fix For: maven-bundle-plugin-1.4.2 > > Attachments: Felix-620.zip > > > It appears to me that if I just invoke *manifest* goal of maven-bundle-plugin, it ignores *_include* instruction, where as if I use *bundle* goal, it is used by the plugin. There are various ways to test it. The easiest seems to be using a non-existent file name. Attached are two sets of pom files, pom.xml uses bundle goal, where as pom.xml.notworking uses manifest goal. While using the first one, bnd complains about missing osgi.bundle3 file, where as it does not report any such error while using the first one. That makes me think that the manifest Mojo is not sending the file name to bnd. > I am attaching a very simple test case along with a README describing the issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.