Uploaded image for project: 'Felix'
  1. Felix
  2. FELIX-699

manifest goal does not interprete _include instruction correctly

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: maven-bundle-plugin-1.4.3
    • Fix Version/s: maven-bundle-plugin-2.0.0
    • Component/s: Maven Bundle Plugin
    • Labels:
      None
    • Environment:
      Maven version: 2.0.7
      Java version: 1.5.0_13-rev
      OS name: "sunos" version: "5.11" arch: "x86"

      Description

      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.

        Activity

        Hide
        sahoo Sahoo added a comment -

        Test case with README

        Show
        sahoo Sahoo added a comment - Test case with README
        Hide
        sahoo Sahoo added a comment -

        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>

        Show
        sahoo Sahoo added a comment - 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>
        Hide
        mcculls Stuart McCulloch added a comment -

        I believe this is because in the manifest goal we're setting the base directory after processing the instructions - reversing these statements should fix the problem.

        targeting next major release (1.6.0) of the maven-bundle-plugin

        Show
        mcculls Stuart McCulloch added a comment - I believe this is because in the manifest goal we're setting the base directory after processing the instructions - reversing these statements should fix the problem. targeting next major release (1.6.0) of the maven-bundle-plugin
        Hide
        mcculls Stuart McCulloch added a comment -

        Fixed in trunk

        Show
        mcculls Stuart McCulloch added a comment - Fixed in trunk
        Hide
        mcculls Stuart McCulloch added a comment -

        Closing as maven-bundle-plugin 2.0.0 has been released.

        Show
        mcculls Stuart McCulloch added a comment - Closing as maven-bundle-plugin 2.0.0 has been released.

          People

          • Assignee:
            mcculls Stuart McCulloch
            Reporter:
            sahoo Sahoo
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development