[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Re: [eclipse.org-planning-council] Re: EclipseCon memory stick and Ganymede M5
|
I would recommend against using 1.6 for this. SWT and the IBM 1.6 JVM are
currently having some nasty interactions on multiprocessor machines. See
the following bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=215252
Product/Component: Platform / SWT
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
Nick
Boldt/Toronto/IBM
@IBMCA To
Sent by: "Cross project issues"
cross-project-iss <cross-project-issues-dev@eclipse.o
ues-dev-bounces@e rg>, "eclipse.
clipse.org org-planning-council"
<eclipse.org-planning-council@eclip
se.org>
02/01/2008 11:16 cc
AM
Subject
Re: [cross-project-issues-dev] Re:
Please respond to [eclipse.org-planning-council] Re:
Cross project EclipseCon memory stick and
issues Ganymede M5
<cross-project-is
sues-dev@eclipse.
org>
If we're going to include JVMs, we should omit 1.4 entirely. EMF and
all EMF-dependent projects need 5.0+. Pack200 requires 5.0+. The JEE
bundle from EPP requires 5.0+ (unless you didn't really want to use
WTP afterall). ;-)
Why give people the whole update site and have discover that half the
stuff they installed is disabled because they're running with an
obsolete JVM?
Should we push the envelope and include 6.0, instead of 5.0?
$0.02,
Nick
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
