2009/9/29 Henri Gomez <[email protected]>

> Hi to all,
>
> I'm trying to use the maven-bundle-plugin 2.0.1 to build RCP
> applications under Eclipse with m2eclipse.
>
> As such, it's an IDE (PDE) driven application and it should follow the
> various meta informations set by Eclipse IDE.
>
> For instance, I'd like to use the MANIFEST.MF but override the
> Bundle-Version with the one from pom.xml like this :
>
>    <plugins>
>
>      <plugin>
>
>        <groupId>org.apache.felix</groupId>
>        <artifactId>maven-bundle-plugin</artifactId>
>        <extensions>true</extensions>
>        <configuration>
>          <instructions>
>              <Bundle-Version>${pom.version}</Bundle-Version>
>              <_include>META-INF/MANIFEST.MF</_include>
>          </instructions>
>        </configuration>
>      </plugin>
>
>    </plugins>
>
> It seems, the Bundle-Version directive is not followed by
> maven-bundle-plugin when <_include>META-INF/MANIFEST.MF</_include> is
> in use.
> Anything to do to overcome this ?
>

does the included META-INF/MANIFEST.MF also contain Bundle-Version?

from http://aqute.biz/Code/Bnd :

   "-include ...

    By default, a property defined in an include file override earlier
definitions,
    this implies that any property in the bnd file is overridden if defined
in an
    include file. The include files are read in the order they are listed
where
    later files override earlier files. If there are multiple definitions
for the same
    property, then the last definitions wins. If the path of an included
file starts
    with a ~, then it will *not* override earlier set properties."

so try:   <_include>~META-INF/MANIFEST.MF</_include>

Btw, a lot of the time the answer can be found in one of the following
links:

  http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
  http://felix.apache.org/site/apache-felix-bundle-plugin-faq.html
  http://www.aqute.biz/Code/Bnd

HTH :)

Regards
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Cheers, Stuart

Reply via email to