[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| 
RE: [mdt-ocl.dev] M6/M7 interim Examples builds
 | 
Hi Anthony,
 
Yes, it was promoted after some time. Ed has 
successfully switched to UML2 M6 in our next builds.
 
Thus, I don't think we should respin our M6 to produce 
M6a - they seem to be identical.
 
Cheers,
- Alex.
Hi Team,
I see UML2 M6 was promoted this 
morning.
Cheers...
Anthony
--
Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software 
Development Manager
IBM Rational Software: Aurora / Modeling Tools 
Phone: 
613-270-4613
Alexander Igdalov ---2010/03/16 07:43:06 AM---Hi 
Ed,
  
  
      From: | 
      Alexander Igdalov 
      <alexander.igdalov@xxxxxxxxx> | 
  
      To: | 
      "'MDT OCL mailing list'" 
      <mdt-ocl.dev@xxxxxxxxxxx> | 
  
      Date: | 
      2010/03/16 07:43 AM | 
  
      Subject: | 
      RE: [mdt-ocl.dev] M6/M7 interim Examples 
      builds | 
Hi Ed,
> Very impressive speed on getting M6 out, 
though I think somehow you
managed to promote before EMF. 
In fact 
there was no magic in our dependency on EMF M6, I started building
OCL after 
it became available. Perhaps, your browser cache could show things
in the 
reverse order... 
The only thing that worries me a little is the dependency 
on UML2 M5 (but
UML2 M6 still isn't there...)
> Did the release 
provoke the temporary buckybuild failure?
Yes, I forgot to update the 
feature ID in the mdt-ocl.build file. The
buckybuild recovered after I did 
it.
> Now we can sort out what to do about builds to support the OCL 
Examples
Editor.
My +1 to approach b). BTW, have you asked Robert 
whether IMP is ok with the
redistribution?
> Alex: when we add 
editor tests, we want to make sure there is a two times
expectation timeout 
on the build since UI tests can easily lock up with an
unanswered "Do you 
want to delete XXX" popup or equivalent.
Ok.
Cheers,
- 
Alex.
-----Original Message-----
From: 
mdt-ocl.dev-bounces@xxxxxxxxxxx
[mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] 
On Behalf Of Ed Willink
Sent: Tuesday, March 16, 2010 12:24 PM
To: MDT OCL 
mailing list
Subject: [mdt-ocl.dev] M6/M7 interim Examples builds
Hi 
All
Very impressive speed on getting M6 out, though I think somehow you 
managed
to promote before EMF. Did the release provoke the temporary 
buckybuild
failure?
--
Now we can sort out what to do about 
builds to support the OCL Examples
Editor.
a) The approach that half 
works in
https://build.eclipse.org/hudson/job/cbi-m2m-qvtd-0.8-nightly/79/
Build 
against the IMP Update Site. This successfully compiles and packs an
Update 
Site but fails prior to testing since the p2 install fails. 
The update site 
could be manually archived, but users need to install IMP
Runtime first 
before installing MDT/OCL Examples.
It may be that IMP 
fixes
https://bugs.eclipse.org/bugs/show_bug.cgi?id=303424
promptly, 
but I think we can sympathise with a lack of enthusiasm for
upgrading build 
procedures. We should expect a significant delay before the
IMP developers 
migrate from Ganymede.
b) The approach that works in
https://build.eclipse.org/hudson/job/cbi-m2m-qvtd-0.8-nightly/70/
Add 
IMP Runtime to the base editor feature and build so that IMP Runtime
comes 
from SVN.
This republishes IMP Runtime on the MDT/OCL Update site and so 
avoids the
problem that the IMP Update Site is not p2-ready; there are no 
artifacts.jar
and contents.jar
When bug 303424 is fixed (by M7 if 
we're lucky) we might revert to a).
With MDT/OCL being part of the Helios 
train and IMP not being, we might
choose to stick with this approach so that 
the Helios modelling package does
not have a dangling dependency on 
IMP.
c) Do nothing
No OCL Examples Editor in Helios.
d) 
Other Ideas
---
I would like some approval/lack of disapproval 
from other committers before
changing Examples features to commit us to a now 
only slightly awkward IMP
dependency.
---
Alex: when we add 
editor tests, we want to make sure there is a two times
expectation timeout 
on the build since UI tests can easily lock up with an
unanswered "Do you 
want to delete XXX" popup or equivalent.
    
Regards
        Ed 
Willink
_______________________________________________
mdt-ocl.dev 
mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
_______________________________________________
mdt-ocl.dev 
mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev