Eclipse Community Forums: UML2 » UML OCL -> Switch to UML 2.2.0

Help

Home

Home » Modeling » UML2 » UML OCL -> Switch to UML 2.2.0

Show: Today's Messages :: Show Polls :: Message Navigator

UML OCL -> Switch to UML 2.2.0 [message #475768]

Wed, 05 September 2007 12:47

Alexander NyÃ?en

Messages: 38
Registered: July 2009

Member

Hallo,

I noticed that the UML verson number was increased from 2.1.1 to 2.2.0. OCL
UML does exclude this version explicitly. As we are using both plugins in
our nightly product build and as we are compiling against their HEAD
versions respectively, we currently have a missing dependency regarding the
two plugins. Will OCL UML be updated soon to reflect the version increment
of UML or do I have to switch to an older version of UML in my nightly build
to overcome this problem?

Best Regards
Alexander

Report message to a moderator

Re: UML OCL -> Switch to UML 2.2.0 [message #475769 is a reply to message #475768]

Wed, 05 September 2007 13:28

james bruck

Messages: 1724
Registered: July 2009

Senior Member

Hi Alexander,

The OCL version incompatibility problems you have noticed should be resolved
no later than next week ( Christian is on vacation until next week ).

The version numbers in UML2 [head] have been updated in preparation for a
build this week but there has not yet been a published 2.2.0 build ( because
of synchronization issues and other minor build problems ). It looks like
you are on the cutting edge :) .

For the time being you could switch from head to the maintenance branch if
you want to get your builds going, but be assured that this problem will be
resolved by next week.

- James.

"Alexander Ny

Report message to a moderator

Re: UML OCL -> Switch to UML 2.2.0 [message #475854 is a reply to message #475769]

Tue, 11 September 2007 21:01

Eclipse User

Originally posted by: cdamus.ca.ibm.com

Hi, James, Alexander,

The reason why OCL has this strict dependency is that it extends the
internal implementation classes of the UML metamodel. As such, we need to
keep in locked step every release to ensure compatibility with any internal
changes that will occur as UML2 regenerates their code from time to time.
of particular sensitivity are the integer constants for feature IDs,
protected method overrides, etc.

OCL will be following UML2's tradition of maintaining an open-ended
"enhancement" in bugzilla to track the regeneration of its Ecore and UML
bindings whenever the metamodels that they extend are regenerated, codegen
templates change, etc.

Cheers,

Christian

James Bruck wrote:

> Hi Alexander,
>
> The OCL version incompatibility problems you have noticed should be
> resolved no later than next week ( Christian is on vacation until next
> week ).
>
> The version numbers in UML2 [head] have been updated in preparation for a
> build this week but there has not yet been a published 2.2.0 build (
> because
> of synchronization issues and other minor build problems ). It looks like
> you are on the cutting edge :) .
>
> For the time being you could switch from head to the maintenance branch if
> you want to get your builds going, but be assured that this problem will
> be resolved by next week.
>
> - James.
>
>
> "Alexander Ny�n" <any@informatik.rwth-aachen.de> wrote in message
> news:fbm8gt$n18$1@build.eclipse.org...
>> Hallo,
>>
>> I noticed that the UML verson number was increased from 2.1.1 to 2.2.0.
> OCL
>> UML does exclude this version explicitly. As we are using both plugins in
>> our nightly product build and as we are compiling against their HEAD
>> versions respectively, we currently have a missing dependency regarding
> the
>> two plugins. Will OCL UML be updated soon to reflect the version
>> increment of UML or do I have to switch to an older version of UML in my
>> nightly
> build
>> to overcome this problem?
>>
>> Best Regards
>> Alexander
>>

Report message to a moderator