[jbosstools-issues] [JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
[
https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-13671:
---------------------------------------------
[~mickael_istria] not following what you meant here:
"It's possible to exclude pom from watched resources for the Git timestamp
provider.
Ideally, we would like to achieve a similar behaviour that would ignore qualifiers, so we
won't have to brainstorm about what's the best qualifier to implement this, Tycho
would take an already built bundle if the content are the same, except qualifier."
Not following how exclude pom from watched resources relates to the latter about
"similar behaviour" and ignoring qualifiers. CAn you elaborate ?
parent pom should use last-mod-timestamp from git for a
plugin/feature instead of current timestamp when building
-----------------------------------------------------------------------------------------------------------------
Key: JBIDE-13671
URL: https://issues.jboss.org/browse/JBIDE-13671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.1.x
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira