Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] RE: [eclipse.org-planning-council] Re: EMF usage in TPTP 4.4.0

A thing that might be worth mentioning is that JDK 7 (Dolphin) is at beta 5
now. According to the Sun support policies
http://java.sun.com/products/archive/eol.policy.html, the completion of a
Java 1.4.2 EOL (End Of Life) is not further away then the GA of Dolphin
(scheduled for 2008) so my guess is that the start of that cycle is close.
The EOL for 1.3.1 started in October 2004 and was complete with the GA
release of Java 6.

Kind Regards,
Thomas Hallgren


-----Original Message-----
From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of
Marcelo Paternostro
Sent: Monday, January 08, 2007 07:39
To: eclipse.org-planning-council
Cc: TPTP PMC communications (including coordination, announcements,and Group
discussions); Cross project issues;
eclipse.org-planning-council-bounces@xxxxxxxxxxx;
eclipse.org-planning-council
Subject: [eclipse.org-planning-council] Re: EMF usage in TPTP 4.4.0

I believe I am reading some misleading information on this thread.  Just to
make sure we are all on the same page, I will try to summarize the technical
details that I think are relevant here.

- A code compiled with Java 1.4 runs on Java 5 without any problem.

- A code compiled with Java 5 does not run with Java 1.4.  Even
'HelloWorld.java' has such "limitation".

- A bundle that has its environment set to require Java 5 is not activated
when Eclipse is executed with Java 1.4.

- EMF 2.3.0 is compiled with Java 5 and all its bundles require Java 5.

- EMF 2.3.0 cannot be compiled with Java 1.4 due to the extensive use of
Java 5.0 features.

- EMF 2.3.0 is binary compatible with our latest release (EMF 2.2.1).
Besides our own tests, we heard this from developers of Eclipse projects and
commercial products.  This means that adopting EMF 2.3.0 is not a problem as
long as the code is not recompiled.  We also verified that  EMF 2.3.0 does
not break anything if the source compatibility of projects are set to Java
1.4,

- EMF 2.3.0 can generate code targeting both Java 1.4 and Java 5.


Putting it together:

- EMF 2.3.0 and its dependencies are not available if Java 1.4 is used.

- If a bundle is compiled with Java 1.4 or with source compatibility set to
Java 1.4, it will run without any problems with EMF 2.3.0 and Java 5.

- To run your code with Java 1.4, you will need a previous version of EMF.
Our latest release is 2.2.1 (available in Callisto) and we are currently
fixing important bugs on the 2.2.2 maintenance stream.


Hopefully this will make it easier to understand the impacts of EMF 2.3.0 on
Europa.

Best regards,

Marcelo Paternostro
IBM Toronto Lab
marcelop@xxxxxxxxxx

_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council



Back to the top