| commit | b427e32c188ecdfed1b0eb75785cb387b13eae26 | |
| author | Igor Fedorenko <igor@ifedorenko.com> | |
| Wed, 6 Jan 2010 23:51:39 +0000 (6 18:51 -0500) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Thu, 7 Jan 2010 02:15:42 +0000 (6 18:15 -0800) | ||
| tree | 6738f9188b3a096a2e3ed86ea6334db5eab52737 | treesnapshot (tar.gz zip) |
| parent | f50294461b6d59f051bfebc68271155c47a7d4d8 | commitdiff |
Use build timestamp as OSGi version qualifier for SNAPSHOT builds
Default maven-bundle-plugin behaviour results in use of the same
.SNAPSHOT OSGi bundle version qualifier for all snapshot builds.
This causes problems for eclipse update manager and other consumers
that rely on OSGi bundle metadata to select "newer" or "best
matching" version of jgit bundle.
To solve the problem, maven-bundle-plugin is configured to replace
.SNAPSHOT with build timestamp in format like 20100106-1234.
Change-Id: I0999c7bd68aa2ee74dffaed54a8dc4e1b67cf80d
Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Default maven-bundle-plugin behaviour results in use of the same
.SNAPSHOT OSGi bundle version qualifier for all snapshot builds.
This causes problems for eclipse update manager and other consumers
that rely on OSGi bundle metadata to select "newer" or "best
matching" version of jgit bundle.
To solve the problem, maven-bundle-plugin is configured to replace
.SNAPSHOT with build timestamp in format like 20100106-1234.
Change-Id: I0999c7bd68aa2ee74dffaed54a8dc4e1b67cf80d
Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| pom.xml | diffblobblamehistory |