[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] HEAD is broken
|
I think Java 1.4 support is a good feature since it allows a wide range
Java 1.4 users to use eclipse/CDT. I believe that a lot of users
continue using Java 1.4 now. Moving to 1.5 could drop them out. However
in case platform decides to switch to 1.5, then we don't have any
choice, and I agree with Chris to not switch the CDT to 1.5 until
platform officially declares its 1.5 switch.
To my mind, not being able to use 1.5 features is much smaller
inconvenience in comparison with not being able to use CDT with Java 1.4
Mikhail
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Chris Recoskie
Sent: Friday, June 30, 2006 6:38 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] HEAD is broken
If the platform supports 1.5 then we should follow suit, however I don't
think we should do this before they officially support it.
I'm not sure that you can build all of Eclipse with 1.5 yet. Last time
I
looked into it there were way too many variables called "enum" etc. that
blew everything up. Maybe they've fixed this by now, I have no idea.
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
Doug Schaefer
<DSchaefer@xxxxxx
m>
To
Sent by: "CDT General developers list."
cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
clipse.org
cc
Subject
30/06/2006 10:26 RE: [cdt-dev] HEAD is broken
AM
Please respond to
"CDT General
developers list."
<cdt-dev@eclipse.
org>
We got that on our internal nightly build as well until I realized that
we
were still building HEAD and not cdt_3_1.
It looks like a 1.5-ism that has crept into HEAD which brings us to the
decision point of whether to switch to 1.5 for CDT 4.0. Since the
platform
will likely be 1.5 I'd say go for it.
Does anyone think they'll still need Java 1.4 next year?
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC member
http://cdtdoug.blogspot.com
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On
Behalf Of Chris Recoskie
Sent: Friday, June 30, 2006 10:22 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] HEAD is broken
Do we have to use the Eclipse 3.3 stream now? I didn't get the memo...
Severity and Description Path Resource Location Creation
Time
Id
assert cannot be resolved to a type
org.eclipse.cdt.ui/src/org/eclipse/cdt/internal/ui/viewsupport
AsyncTreeContentProvider.java line 172 1151676738562 6580
assert cannot be resolved to a type
org.eclipse.cdt.ui/src/org/eclipse/cdt/internal/ui/viewsupport
AsyncTreeContentProvider.java line 321 1151676738562 6584
Syntax error on token ".", = expected
org.eclipse.cdt.ui/src/org/eclipse/cdt/internal/ui/viewsupport
AsyncTreeContentProvider.java line 172 1151676738562 6581
Syntax error on token ".", = expected
org.eclipse.cdt.ui/src/org/eclipse/cdt/internal/ui/viewsupport
AsyncTreeContentProvider.java line 321 1151676738562 6585
The method getCurrent() is undefined for the type
AsyncTreeContentProvider
org.eclipse.cdt.ui/src/org/eclipse/cdt/internal/ui/viewsupport
AsyncTreeContentProvider.java line 172 1151676738562 6582
The method getCurrent() is undefined for the type
AsyncTreeContentProvider
org.eclipse.cdt.ui/src/org/eclipse/cdt/internal/ui/viewsupport
AsyncTreeContentProvider.java line 321 1151676738562 6586
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev