Thanks for your answer.
That seems to be the problem: I mixed both plugins.
The idea was to insert the build number in the manifest via the super
pom of my projects in order to avoid modifying all modules. Thus I
inserted in the Super POM:
|<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.1</version>
<configuration>
<archive>
<manifest>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
</manifest>
<manifestEntries>
<Implementation-Build>${buildNumber}</Implementation-Build>
</manifestEntries>
</archive>
</configuration>
</plugin>|
By inheritance, each bundle would have included the build number in its
manifest.
If this does not work (mixing maven-bundle-plugin and maven-jar-plugin),
then I guess I have to change the POM of all my modules, because if in
the super POM I insert:
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<configuration>
<instructions>
<Implementation-Build>${buildNumber}</Implementation-Build>
</instructions>
</configuration>
</plugin>
It will be overwritten by the bundle configuration of my modules.... Not
very handy. But is there another way?
Kind regards
Le 04/10/2012 00:19, Allen Lau a écrit :
buildnumber-maven-plugin definitely works. Use maven-jar-plugin or
maven-bundle-plugin depending on your package type. Don't mix them up. I
would recommend that you use the "bundle" type and the maven-bundle-plugin
for building OSGi apps. Try turning on debug with mvn -X to see what's
going on.
On Wed, Oct 3, 2012 at 5:43 AM, Benoît Thiébault <[email protected]>wrote:
Hi everyone,
I don't know if this mailing list is the right place to post my question...
I am developing OSGi applications that are managed by Maven (and
maven-bundle-plugin in particular) and I would like to provide the SVN
revision number in the bundle MANIFEST.
There are two Maven plugins that I am aware of that provide this
functionality. They are namely:
- maven-svn-revision-number-**plugin, http://code.google.com/p/**
maven-svn-revision-number-**plugin/<http://code.google.com/p/maven-svn-revision-number-plugin/>
- buildnumber-maven-plugin, http://mojo.codehaus.org/**
buildnumber-maven-plugin/<http://mojo.codehaus.org/buildnumber-maven-plugin/>
While both of them work perfectly on standard <package>jar</package> Maven
modules, they both fail with <package>bundle</package> Maven modules.
How do you do this in OSGi context? Are there other Maven plugins
available that work well with BND? If this is a BND bug, can it be fixed?
I have asked questions on the subject here http://stackoverflow.com/**
questions/12604161/error-**while-adding-svn-revision-in-**
jar-manifest-with-maven-and-**maven-bundle-plug<http://stackoverflow.com/questions/12604161/error-while-adding-svn-revision-in-jar-manifest-with-maven-and-maven-bundle-plug>and
there
https://groups.google.com/**forum/?fromgroups=#!topic/**
maven-svn-revision-number-**plugin/yvHvn1tS_2M<https://groups.google.com/forum/?fromgroups=#!topic/maven-svn-revision-number-plugin/yvHvn1tS_2M>without
success so far.
Kind regards,
Benoît
