Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] OCL and UML causing Helios aggregation build break?

Hi David,

I did actually reply to you and the interested parties before you sent this email ...

This has to do with UML2 moving up a minor version number for the first time in the release.   I believe that OCL has a version dependency on [3.0.0, 3.1.0)   (not inclusive) of UML but we are now at version 3.1.0.

I believe the OCL component would need to respond by changing the version range check.

I could temporarily back out those changes so Helios is fixed but I think the proper way to address this is for OCL to create another build with updated version range checking.

- James.

From: David M Williams <david_williams@xxxxxxxxxx>
To: cross-project-issues-dev@xxxxxxxxxxx
Date: 07/12/2009 10:12 AM
Subject: [cross-project-issues-dev] OCL and UML causing Helios aggregation        build break?
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

The Helios aggregation build has been broken since Friday.

Anyone know why?

The "auto blame" heuristics pick MDT OCL and MDT UML and several emails sent to those teams.

Worse than the break itself, I have not heard a word from those teams.

We are starting our "ramp up" to M4 so it is very important to keep the build clean.

If anyone knows what's up with these components/builds please let us know (soon).
Otherwise, I'll just start removing stuff until it builds and removed projects will need to figure out
how to get back in.


cross-project-issues-dev mailing list

Back to the top