Hi
slave1 has three jobs that look like they are waiting for a Hudson
restart.
two runs on fastlane give a stupid temporarily unavailable error.
Will a maintenance build work on branch tests on fastlane? Is
fastlane broken too?
Ed
On 15/02/2012 18:36, Ed Willink wrote:
Hi
Bug/371659 branch currently queued for practice build.
Ed
On 15/02/2012 18:27, Ed Willink wrote:
Hi Adolfo
Bug 371569 raised to change the com.google.collect from require
bundle to import package, which then is compatible with Xtext
2.2.1.
If I get a practice maintenance build done soon can be we get
this in RC4?
Regards
Ed
On 15/02/2012 13:50, Adolfo Sánchez-Barbudo Herrera wrote:
Hi Ed,
No problem about any suffix/preffix from the releng point of
view. It's as easy as including it in the Build Alias. If we
finally create new release after Indigo SR2, I'm also inclined
to add some description specifically for the Category Name.
For instance:
Eclipse OCL 3.1.2 (Xtext 2.2.1 compatible)
However, since Xtext ships 2.1.2 into Inidigo SR2, I hope
there is not a real need for a new Release.
Regards,
Adolfo.
El 15/02/2012 7:17, Ed Willink escribió:
Hi
Xtext 2.2.1 for (SR2) appears to have changed 'internal'
APIs and so attempting to run OCLinEcore 3.1.1 with Xtext
2.2.1 gives editor instantiation
failures.https://bugs.eclipse.org/bugs/show_bug.cgi?id=371574.
While this is clearly an Xtext problem, it isn't going to be
fixed for SR2 or SR2a, we can just hope that itemis learn
how many of their 'internal' APIs are actually external and
avoid the problem in the future.
Anyway it is our user's problem, so I think we need to
create a 3.1.2X release in which we regenerate editors and
raise the lower bound on Xtext to 2.2.1 to force
compatibility. This is of course not allowed in an SR, so it
isn't an SR as such. Is an X suffix enough, or do we want a
longer more distinct name? Adolfo: is there any spelling
that is particularly easy for releng?
Regards
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 message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2112/4810 - Release
Date: 02/14/12
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2112/4811 - Release
Date: 02/15/12
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
No virus
found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2112/4811 - Release Date:
02/15/12
|
