BTW,
If it has not been clear enough. I prefer to simply remove the
examples feature from the Indigo's build during 25-26 jan time
frame.
Best Regards,
Adolfo.
El 20/01/2011 10:49, Adolfo Sánchez-Barbudo Herrera escribió:
Ed,
Indigo aggregation uses (should use) milestones repositories, so
no pain here (until the 7th Feb :) ).
The point is if we want to bother any potential clients which are
using bleeding-edge stuff (that is feeding their builds using
MDT/OCL and Xtext nightly repositories) between the 26th and
28th...
Giving that the probability of bothering clients (which should
know the risks of using the nightly repository) is nearly null and
the time frame is only two days, I'm inclined now to do
nothing.... as soon as (let's say the 28th jan) the code is
aligned to Xtext 2.0.0 I'll create a new Integration build for
downstream projects... the 7th feb we will contribute to indigo
aggregation with a new stable build.
Mmm.... forget everything I've written so far ..... after reading
Sven email again, I understood know that they are anticipating the
breaks into the indigo aggregator with Xtext 2.0.0 (using their
nightly repository, I guess)... so let's do what we have arranged
Concerning the OCL Console... The easiest to me is removing the
examples feature from the Indigos build.... otherwise, either I'd
have to remove the xtext plugins from the feature (it's not
sensible) or I'd have to look up in buckminster documentation a
way to properly do that. I could try to ask into the buckminster
forums, although I'm not very happy with them after passing my
help-to-fix-our-build request out
Best Regards,
Adolfo.
El 20/01/2011 10:11, Ed Willink escribió:
Hi Adolfo
I agree that probably no other project depends on OCL examples;
just possibly the OCL console.
The problem at M1 was for the Indigo aggregation that currently
treats all of OCL as one contribution, so we need to reduce the
size of OCL temporaily.
Removing the entire example feature should be fairly simple. ...
Ah actually, even simpler is removing everything except the OCL
console, that way the features all exist, it's just a matter of
deleting all bar one of the entries in the examples feature.xml.
Regards
Ed
On 20/01/2011 09:58, Adolfo Sánchez-Barbudo Herrera wrote:
Ed,
Indigo M5+1 is the 7th in February (two weeks to align with
Xtext 2.0.0). Concerning the builds:
1. I don't think that our downstream projects were affected
the 26th unless they also depended on Xtext and they used
Xtext nightly p2 repository.
2. If so, they could be collapsed anyway if they were using
any MDT/OCL milestone or integration builds (contains "old
examples")
3. If downstream projects depended on MDT/OCL and Xtext and
used MDT/OCL and Xtext nightly p2 repositories, then as you
suggest we would have to do a manual build to create said
nightly p2 repository without examples.
I guess that we should do your suggestion, just in case...
I'll plan the change on Wednesday, the 25th January in the
morning.
Best Regards,
Adolfo.
El 19/01/2011 16:51, Ed Willink escribió:
Hi Adolfo
It will be difficuilt to precisely synchronise Xtext and OCL
during the Xtext upgrade, so to reduce problems for the
Indigo build, I suggest we contribute a without-examples OCL
to Indigo on the 24th, ensuring that the various projects
dependent on OCL don't collapse on the 26th when Xtext
changes.
Also on the 24th I'll promote the branch for Xtext 2.0, and
on the 28th we will aim to once again contribute a
with-examples OCL build to Indigo.
If you're ok with this I'll annouce it to
cross-project-issues-dev.
Regards
Ed
-------- Original Message --------
Hi all,
the Xtext 2.0 HEAD will be promoted to the Indigo build on Jan 26th.
So we'll have roughly two weeks to fix any remaining issues before M5.
Thanks,
Sven
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1191 / Virus Database: 1435/3389 - Release Date: 01/18/11
_______________________________________________
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: 10.0.1191 / Virus Database: 1435/3391 - Release
Date: 01/19/11
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|
