+1 From: papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] On Behalf Of Remi Schnekenburger Sent: Friday, January 06, 2017 12:22 PM To: papyrus-rt-dev@xxxxxxxxxxx Subject: [papyrus-rt-dev] Dependency on Core Papyrus Hi team, Since we are targeting a Papyrus-RT release based on latest release from Papyrus, what about moving the build jobs to depend on the papyrus release Neon.2 rather than nightly ? i.e. papyrus.kind=papyrusreleases rather than papyrus.kind=papyrusnightly in the build job configurations. That would give use a more stable platform, and we would ensure that we already test against latest release version, and do not introduce dependencies towards nightly APIs. I proposed a gerrit [1] to update target platforms for Papyrus release folder, the TPs now target the release neon.2. All gerrit builds are green, but they depend on the nightly TPs, so that's not relevant... At the same time, I updated the junit util feature dependency to be lazy, as there is no stable release we can rely on. That may be the cause of the failing job about quality. That was also proposed by Céline in a unmerged patch.
-- Remi Schnekenburger
Senior Software Architect / General Manager EclipseSource Paris
Email: rschnekenburger@xxxxxxxxxxxxxxxxx Web: http://eclipsesource.com/paris Mobil: +49 89 21 555 30 - 25 Phone: +49 89 21 555 30 - 25 Fax: +49 89 21 555 30 - 19
EclipseSource France SAS 7 rue de la Croix Martre 91873 Palaiseau
General Manager: Remi Schnekenburger |