[
https://issues.apache.org/jira/browse/FELIX-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625314#action_12625314
]
Sahoo commented on FELIX-699:
-----------------------------
Work around:
Fortunately, there is a simple work around to this bug. While including the
file, use fully qualified path like this:
<_include>${basedir}/osgi.bundle</_include>
> manifest goal does not interprete _include instruction correctly
> ----------------------------------------------------------------
>
> Key: FELIX-699
> URL: https://issues.apache.org/jira/browse/FELIX-699
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.3
> Environment: Maven version: 2.0.7
> Java version: 1.5.0_13-rev
> OS name: "sunos" version: "5.11" arch: "x86"
> Reporter: Sahoo
> Attachments: Feliz-699.zip
>
>
> I have a multi-module project. I configure the maven-bundle-plugin (version
> 1.4.3) in <builds><plugins> section of parent pom.xml. One of the
> configuration instruction is to include a bnd configuration file called
> osgi.bundle. I use manifest goal of maven-bundle-plugin. I see that the
> plugin/bnd is complaining about a missing osgi.bundle file, although the
> module being built has such a file. If I switch to using bundle packaging
> type, the problem goes away. I am attaching a simple test case to demonstrate
> the problem. What is more interesting to note is that, if I cd to the
> submodule and do a build, it builds fine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.