I mostly agree with this approach but this is also the sort of
thing that will get put off and put off until it is too late or too hard and then
we just end up with status quo (whatever that happens to be).
So , as long as everyone understands and accepts that just ‘cause
the code is written using 1.5 today does not mean that that is the way it will
ship, then we should be fine.
+1 on the list of summit topics
Jeff
From:
eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx
[mailto:eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx] On Behalf Of Kevin
McGuire
Sent: Thursday, April 17, 2008 3:35 PM
To: E4 developer list
Subject: Re: [eclipse-incubator-e4-dev] e4 and J2SE-1.5
I seem to
recall we needed a 1.5 vm for the servlet stuff to work properly but that may
not be true or if true may be solved a different way.
>>At this point, I would regard plug-in dependencies as
purely incidental.
Agree. We should understand the requirements
for having a 1.5 vm, and base the decision on that.
|
Boris
Bokowski/Ottawa/IBM@IBMCA
Sent by:
eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx
04/17/2008
02:02 PM
|
Please respond to
E4 developer list <eclipse-incubator-e4-dev@xxxxxxxxxxx>
|
|
|
To
|
E4
developer list <eclipse-incubator-e4-dev@xxxxxxxxxxx>
|
|
cc
|
E4
developer list <eclipse-incubator-e4-dev@xxxxxxxxxxx>,
eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx
|
|
Subject
|
Re:
[eclipse-incubator-e4-dev] e4 and J2SE-1.5
|
|
> Has there been a decision for e4 to use
J2SE-1.5?
I don't think any decision has been made in this regard. At this point, I
would regard plug-in dependencies as purely incidental.
We should add this topic to the Summit agenda though.
Boris
_______________________________________________
eclipse-incubator-e4-dev mailing list
eclipse-incubator-e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
