[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [birt-pmc] Feedback on move to EMF 2.3. TPTP (andothers) arecontinuing with EMF 2.2.2
|
Title: Message
Mike
Since
some new features and bug fixes in BIRT 2.2 depends on WTP and DTP that is
only avaiable in the Europa release train, unless these projects also support
Eclipse 3.2 with their Europa code base, we will not be able to have the a
single release (feature set) on both Eclipse 3.3 and Eclipse 3.2.
While
we do not see a need to exploit
EMF 2.3 new features, I think it is
too limited if we can not exploit any Eclipse platform 3.3 new
features.
+1 on
version support practise discussion.
Wenfeng
Could we also
support Eclipse 3.2, EMF 2.2.2, and JDK 1.4.2 for BIRT 2.2? Not
requiring Java 1.5 simplifies migration to BIRT 2.2 a lot. Not requiring
a new Eclipse would make it pretty much a "drop it in" for those who don't
want to simultaneously update their environment.
I know this doubles the testing load.
Are there any standards or recommended
practices relating to version support and dropping old versions? We can
talk about this at a PMC meeting. Most products have policies on this to
minimize jerking around their customers, and we should look at BIRT this way.
Even something simple like one version notice/overlap before we drop
support for an environment would help. That way we could support Eclipse
3.2 and 3.3 with BIRT 2.2, and drop 3.2 with BIRT 2.3 (or whatever is next).
If we want to go to java 1.5, we could notify the community that BIRT
2.2 will be the last release to support java 1.4.2. This would give 1
year notice so people could plan. We have a lot of products looking to
incorporate BIRT, and they can't always change their environment quickly
because of commitments to our customers.
Mike
"Wenfeng Li"
<wli@xxxxxxxxxxx>
Sent
by: birt-pmc-bounces@xxxxxxxxxxx
01/12/2007 02:33 PM
|
Please respond
to
"BIRT PMC communications \(including coordination,
announcements, and Group discussions\)"
<birt-pmc@xxxxxxxxxxx> |
|
|
To
| "BIRT PMC communications
\(including coordination, announcements,
and Group discussions\)" <birt-pmc@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| RE: [birt-pmc] Feedback on move
to EMF 2.3. TPTP (and others)
arecontinuing with EMF 2.2.2 |
|
Since BIRT does
not exploit EMF 2.3 new features, I think it is a good work around to stay on
EMF 2.2.2. + JDK 1.4. How about we use Eclipse 3.3 + EMF 2.2.2 + JDK
1.4. environment for BIRT 2.2 build and development?
And we can test
the binary on Eclipse 3.3 + EMF 2.3 + JDK 1.5.
Wenfeng
-----Original
Message-----
From: birt-pmc-bounces@xxxxxxxxxxx
[mailto:birt-pmc-bounces@xxxxxxxxxxx] On Behalf Of Scott
Rosenbaum
Sent: Friday, January 12, 2007 7:03 AM
To: 'BIRT
PMC communications (including coordination, announcements,and Group
discussions)'
Subject: RE: [birt-pmc] Feedback on move to EMF 2.3.
TPTP (and others) arecontinuing with EMF 2.2.2
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 _______________________________________________
birt-pmc mailing
list
birt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/birt-pmc
