[
https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13671:
------------------------------------
[~mmalina] well, the only alternative that comes to mind is to have publishing happen as a
manual step performed by leads when they decide it's time for a new build to be
pushed.
So we could have:
Projects build against latest PUBLISHED integration build [in a new composite site]
Aggregates build against latest PUBLISHED integration build [in a new composite site]
Projects publish by default to staging/\{JOB_NAME\} as they do today
Projects MANUALLY copy bits from staging/\{JOB_NAME\} to integration/\{project name\} when
they want the downstream consumers to get something new.
Of course the problem there is that it requires that people remember to do the publish.
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.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 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