[
https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi...
]
Denis Golovin commented on JBIDE-13671:
---------------------------------------
{quote}The whole point here is that it no longer matters in which build the bits are built
because we know they're coming from the same SHA in github. So we could add that
suffix back onto the update site version qualifier if we want but I'm not sure we need
it.{qote}
Then we have to go all the way and remove build label from version and stop changing
versions for plugins/features all together.
How do we map timestamp back to SHA?
Is there SHA in manifest somewhere?
Replace build timestamp in qualifier by last-mod-timestamp from git
-------------------------------------------------------------------
Key: JBIDE-13671
URL:
https://issues.jboss.org/browse/JBIDE-13671
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Optional
Fix For: 4.4.0.Alpha2
Attachments: jbide13671-before-and-after.png
This needs to be added to master parent pom:
{code}
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-packaging-plugin</artifactId>
<version>${tycho.version}</version>
<dependencies>
<dependency>
<groupId>org.eclipse.tycho.extras</groupId>
<artifactId>tycho-buildtimestamp-jgit</artifactId>
<version>${tycho-extras.version}</version>
</dependency>
</dependencies>
<configuration>
<strictBinIncludes>false</strictBinIncludes>
<format>'v'yyyyMMdd-HHmm</format>
<timestampProvider>jgit</timestampProvider>
<jgit.ignore>
</jgit.ignore>
</configuration>
</plugin>
{code}
Ref:
http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)