Hi,
<packaging>bundle</packaging>
<version>1.0.${buildNumber}</version>
That will not work....cause at the time this will be expanded the build
number plugin has not ran ...yet...this would mean to re-read the pom
and interpret it a second time...(which maven doesn't do!)....
While building the bundle I see in the console:
[INFO] Storing buildNumber: 54 at timestamp: 1309442078694
so the plugins is getting the version number correctly but my jar file has
still the "${buildNumber}" thing in its name ...
What you can do is to change the name of the resulting artifact by using
<finalName>....${buildNumber}</finalName>
Or
A good place to put the information is into the MANIFEST.MF file...can
be achieved by using the Maven Jar Plugin
(http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html)..
But usually i would say the version number is enough (like 1.2.3 etc.)
...a kind of buildNumber or Version number (from VCS) is not a good idea...
I've also changed the packaging to jar and then it's working !!! but it
isn't an installable bundle for smx...
The param -DbuildNumber=123 is working too.
See explanation at the top...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
