Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [mdt-ocl.dev] M7a and Xtext API change
Hi Ed,
 
FYI, OCL M7a is out. However, I've had a number of unusual errors during promotion - I will investigate them tomorrow.
 
Cheers,
- Alex.

From: mdt-ocl.dev-bounces@xxxxxxxxxxx [mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Ed Willink
Sent: Sunday, May 09, 2010 10:16 AM
To: MDT OCL mailing list
Subject: Re: [mdt-ocl.dev] M7a and Xtext API change

Hi Alex
I don't understand why yours M7a wasn't signed unlike your next I-build...
Signing is yet another authorization area. Currently you are the only MDT/OCL signer.

It seems that "S" is both stable and signed, so I can do sensible I builds but not S builds.
Regarding the error messages during promotion - you can ignore them, the
default group which is already there is correct. However, I will look into
it and try to avoid the errors.
It would be nice to understand them, because I have to repeat this for an unclear QVTd project path.
I will produce M7a this weekend.
Thanks. Just repeat (#90 - my M7a, or #91 - my I-build).

Could you investigate why the examples plugins don't go into the staging area. I think we need the plugins in that area if the Modeling Discovery UI is to offer to install the MDT/OCL Examples.

I hope to commit some important fixes to examples.xtext today. I'm not sure that I'll have useful CVS access until next Sunday (16th) when I hope to commit further examples.xtext enhancements just in time for RC1 on Monday 17th. I hope nothing else now changes to cause another 2 days of build nightmare.

    Regards

        Ed
Regards,
- Alex.

-----Original Message-----
From: mdt-ocl.dev-bounces@xxxxxxxxxxx
[mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Ed Willink
Sent: Friday, May 07, 2010 6:15 AM
To: MDT OCL mailing list
Subject: Re: [mdt-ocl.dev] M7a and Xtext API change

Hi
  
We therefore need an M7a built against Xtext M7 after regenerating to 
use the M7 APIs.

Since this only affects the editors, existing users don't need it. 
I'll try to do it by myself and see if I can promote. This no doubt 
will mean that M7a is unsigned. I'll recommit the rolled back fix for 
Bug 311625 in M7a.

    
I built an M7a, but indeed it wasn't signed, with a few associated errors so
I didn't promote it.

I then produced an I-build and promoted it. There were numerous accompnaying
permission diagnostics ending:

     [chmod] /bin/chmod: changing permissions of
`/home/data/httpd/download.eclipse.org/modeling/mdt/ocl/3_0/updates/interim/
plugins/org.eclipse.ocl_3.0.0.v201004240200.jar.pack.gz': 
Operation not permitted
     [chmod] /bin/chmod: changing permissions of
`/home/data/httpd/download.eclipse.org/modeling/mdt/ocl/3_0/updates/interim/
site.xml': 
Operation not permitted
     [chmod] Result: 1
     [chgrp] /bin/chgrp: invalid group `mdtadmin'

  but the build appears on the Download page anyway.

Any clues?

Alex you'll need to do the M7a build.

     Ed
_______________________________________________
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


No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 9.0.819 / Virus Database: 271.1.1/2857 - Release Date: 05/06/10 07:26:00

Back to the top