[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| Re: [papyrus-rt-dev] Papyrus-RT-Master-Tooling build is failing | 
| 
Hi Peter,
   You’re right, Tooling should not need Codegen.
 As mention by Christian, the next issue to treat after the 0.8 release would be the test dependencies between Tooling
 and Core that must be resolved to keep a TP as light as possible.  And keep the Core component fully independent from the Tooling Component.
   See also Bug 500556 :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=500556   Best regards Céline         
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Christian DamusEnvoyé : jeudi 6 octobre 2016 16:42
 À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
 Objet : Re: [papyrus-rt-dev] Papyrus-RT-Master-Tooling build is failing
   
The builds should be okay, now.  I’ve got the Codegen and Tooling builds on TPs that include only their actual requirements (tooling
 no longer taking in codegen, for example).  Unfortunately, the same cannot yet be done for the Core build as long as its JUnit tests require Tooling bundles.   
Let us know if there are further problems.   On 6 October, 2016 at 10:10:28, Christian Damus (give.a.damus@xxxxxxxxx)
 wrote: 
I can have a look (seem to be in a releng groove of late), but the bigger question for me is what happened to the history of successful
 builds of codegen component?  How is it back to build #1?     On 6 October, 2016 at 10:01:03, Peter Cigéhn (peter.cigehn@xxxxxxxxx)
 wrote: 
I was planning on verifying a few Bugzillas that Ansgar have merged in. But when I check Hudson I can see that the Papyrus-RT-Master-Tooling
 builds are failing: 
When looking into the logs, it seem like it fails on accessing the build result from Papyrus-RT-Master-Codegen (which never has been built
 sucessfully). Is it really intended that tooling shall depend on codegen? 
Anyway, could someone who have some insight into the build system please take a look at this, so that we can proceed on testing merged
 fixes? _______________________________________________papyrus-rt-dev mailing list
 papyrus-rt-dev@xxxxxxxxxxx
 To change your delivery options, retrieve your password, or unsubscribe from this list, visit
 https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
 | 
BEGIN:VCARD
VERSION:2.1
X-MS-SIGNATURE:YES
N;LANGUAGE=fr;CHARSET=Windows-1252:Céline;JANSSENS
FN;CHARSET=Windows-1252:JANSSENS Céline
ORG:ALL4TEC
TITLE;CHARSET=Windows-1252:Ingénieur d'Etude  Papyrus Support Manager
TEL;WORK;VOICE:+33 2 44 47 23 23
ADR;WORK;PREF;ENCODING=QUOTED-PRINTABLE:;;Parc CERES Bat. L=0D=0A=
2 rue Ferdinand Buisson;CHANGE;;53810;France
LABEL;WORK;PREF;ENCODING=QUOTED-PRINTABLE:Parc CERES Bat. L=0D=0A=
2 rue Ferdinand Buisson=0D=0A=
53810 CHANGE
X-MS-OL-DEFAULT-POSTAL-ADDRESS:2
EMAIL;PREF;INTERNET:celine.janssens@xxxxxxxxxxx
X-MS-OL-DESIGN;CHARSET=utf-8:<card xmlns="http://schemas.microsoft.com/office/outlook/12/electronicbusinesscards" ver="1.0" layout="left" bgcolor="ffffff"><img xmlns="" align="fit" area="16" use="cardpicture"/><fld xmlns="" prop="name" align="left" dir="ltr" style="b" color="000000" size="10"/><fld xmlns="" prop="org" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="title" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="telwork" align="left" dir="ltr" color="d48d2a" size="8"><label align="right" color="626262">Bureau</label></fld><fld xmlns="" prop="email" align="left" dir="ltr" color="d48d2a" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="addrwork" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/></card>
REV:20160907T143407Z
END:VCARD