You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Stuart McCulloch (JIRA)" <ji...@apache.org> on 2008/07/07 11:43:31 UTC

[jira] Commented: (FELIX-620) manifest goal of maven-bundle-plugin ignores _include instruction

    [ https://issues.apache.org/jira/browse/FELIX-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610934#action_12610934 ] 

Stuart McCulloch commented on FELIX-620:
----------------------------------------

Actually the include instruction is being processed, but the manifest goal is not reporting the errors/warnings from Bnd.
I have just added code to report these errors/warnings, and the testcase now behaves the same for both of the goals.

> 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.