Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Re: EMF usage in TPTP 4.4.0

There is no broken process. I remember well the discussions in June. Api compatibility would be preserved, and as long as we didn't want to exploit new features we would not need to move to Java 5. We also discussed the option of having split packaging for each environment. Thinking selfishly this might imply that Europa would be very meaningful when running on 1.4.

In hindsight it is clear that if anyone in Europa wanted to exploit EMF 2.3 or Java 5, all of Europa would get there by default. I am assuming someone is requiring EMF at 1.5 and that is why we are having this discussion.

As you know TPTP has had another release since Callisto and we are admittedly late to the Europa train.

We have changed our build and are doing the needed testing to confirm the Europa configuration. Once that is all out of the way we will explore and confirm all the other parts at play here.

Thanks for your time.
Harm Sluiman, STSM,  
phone:905-413-4032   fax: 4920  
cell: 1-647-300-4758
Admin : Arlene Treanor atreanor@xxxxxxxxxx  Tie: 969-2323 1-905-413-2323

Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>

01/07/2007 01:41 PM

Harm Sluiman/Toronto/IBM@IBMCA
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>, "TPTP PMC communications \(including coordination, announcements, and Group discussions\)" <tptp-pmc@xxxxxxxxxxx>, "" <>
Re: EMF usage in TPTP 4.4.0

While I await the the results of your testing, my understanding from talking to Ed and Nick recently and listening to their explanations of this change to the Councils back in June and again in October was that the runtime will continue to work on JVM 1.4. So as long as you do not regenerate your models, the code will continue to work on JVM 1.4 without change or reduced functionality. I also assume, but have not verified, that you could always re-generate your models using an older EMF and thus continue to use JVM 1.4 with newer models.

The part that puzzles me most is how our process broke down - the EMF team clearly brought this JVM 4/5 issue forward over seven months ago so why is it suddenly a surprise and a blocking issue for Europa? I'd like to resolve that mystery so that we, collectively, don't have similar problems from other known-in-advance project interactions.

- Bjorn

Harm Sluiman wrote:

I believe you have it correct Bjorn. The concern is that given that many of the higher level tools (TPTP, WTP, BIRT) use EMF, the "reduced functionality" may be rather significant. It seems that with  a common component like EMF requiring 5 the majority of configurations above base JDT will require 5. This can make the out of the box experience for a default 1.4 user problematic.

Back to the top