Re: [platform-releng-dev] Our consumption of JDT for the Nightly build

[David M Williams <david_williams@xxxxxxxxxx>]

latest milestone is our routine practice
(unless the JDT team asks for something else). That is, after every milestone,
we updated the JDT Compiler just produced in milestone N-1, to produce
the next milestone N. 

For maintenance it's similar, but different
in that we use only the compiler from that maintenance stream. So for example,
in the end, SR1 is produced with the compiler released with SR1. 

The version in use at any time, can
be seen in the parent pom, in the variable cbi-jdt-version.

Why do you ask? 




From:      
 Lars Vogel <lars.vogel@xxxxxxxxxxx>
To:      
 "Eclipse platform
release engineering list." <platform-releng-dev@xxxxxxxxxxx>,

Date:      
 11/19/2014 09:24 AM
Subject:    
   [platform-releng-dev]
Our consumption of JDT for the Nightly build
Sent by:    
   platform-releng-dev-bounces@xxxxxxxxxxx

---

Hi,

how to we in platform consume JDT in our platform cbi
build? 

Is this based on the latest nightly JDT or on the weekly integration build
or on the milestone build?

Best regards, Lars

-- 
Geschäftsführer

vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx,
Web: http://www.vogella.com_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev