Mike,
There is a bug in the EMF project
that provides some of the rational for the change (79768). It appears
that the EMF team wants to be able to generate java code that takes advantage
of 1.5 functions (Enums, etc.) As recently as 11/15 it appears that the
plan was to maintain support for reverse compatibility based on a perspective
setting.
Hope that
helps,
Scott
From:
birt-pmc-bounces@xxxxxxxxxxx [mailto:birt-pmc-bounces@xxxxxxxxxxx] On Behalf Of Michael Fox
Sent: Friday, January 12, 2007 8:43
AM
To:
birt-pmc@xxxxxxxxxxx
Subject:
[birt-pmc] Feedback on move to EMF 2.3. TPTP (and others) are continuing with
EMF 2.2.2
It seems that not all
projects are moving to 1.5 because of EMF. I would really
encourage staying with EMF 2.2.2 if we are not exploiting anything new in EMF
2.3. Being able to run with Eclipse 3.2, Java 1.4 would make
adopting Europa much easier.
Can we find out
if any BIRT work is dependent on EMF 2.3? If any is, I'll ask if the
value of the new work is worth the pain of causing the world to upgrade, and
if there is any other way to implement the new functionality.
Mike
-----
Forwarded by Michael Fox/Lexington/IBM on 01/12/2007 09:31 AM
-----
|
Harm
Sluiman/Toronto/IBM@IBMCA
01/11/2007 06:13
PM |
|
To |
Michael
Fox/Lexington/IBM@IBMUS |
|
cc |
SWG-BIRTInterest,
Marius Slavescu/Toronto/IBM@IBMCA
|
|
Subject |
Re: BIRT V2.2
(Europa) will require Eclipse 3.3 and Java 1.5Link |
|
Mike, BIRT does not have to
move to 1.5 if they do not want to exploit EMF 2.3. TPTP and others are
continuing to build using EMF 2.2.2 targeting 1.4 and that result is binary
compatible with EMF 2.3. There is also discussion about packaging both
levels of EMF in Europa and IES so that they do not trigger everyone to
require 1.5 just because EMF 2.3 does.
Thanks for
your
time.
--------------------------------------------------------------------------
Harm
Sluiman, STSM,
mailto:sluiman@xxxxxxxxxx
|
Michael
Fox/Lexington/IBM@IBMUS
01/11/2007 10:20
AM |
|
To |
SWG-BIRTInterest
|
|
cc |
|
|
Subject |
BIRT V2.2
(Europa) will require Eclipse 3.3 and Java
1.5 |
|
It turns out that the next
functional BIRT release (V2.2, part of the Europa simultaneous Eclipse
release) will require Eclipse 3.3 and Java 1.5 runtime. The reason for
this is that EMF 2.3 will require that environment, so everything that
includes EMF has to also. I had previously asked about the desirability
of requiring an upgrade to Eclipse 3.3 or continuing to run on the current
Eclipse 3.2. The response was a unanimous desire to be able to continue with
Eclipse 3.2. I passed this on to the BIRT PMC, and we agreed to make
every effort to not require an Eclipse upgrade. However, the interaction
between all the different Eclipse projects make that infeasible.
The move to the new EMF will
be in the V2.2 milestone 4 version which will be available soon. That
milestone release will not run with Eclipse 3.2. Europa is scheduled for
June 2007.
Please let me know if this
will be a major problem for you. The PMC discussed options such as
continuing to enhance the V2.1 stream after V2.2 is released, but obviously
the cost would be extremely high to do the work twice, QA everything twice,
support 2 product streams, etc.
Mike
