Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] HEAD is broken

Yes, I think we've talked about it in the past. We've agreed that CDT 3.1.x
needs to stay on Java 1.4. I haven't heard an official story about Eclipse
3.3, but everyone is assuming they'll drop 1.4. So in the end, we may not
even have the choice.

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 John Cortell
Sent: Friday, June 30, 2006 10:32 AM
To: CDT General developers list.; CDT General developers list.
Subject: RE: [cdt-dev] HEAD is broken

I for one would be very disappointed if CDT didn't adopt 1.5. I'm 
itching to use the new language features. My understanding all along 
was that the platform would adopt 1.5 once 3.2 went out the door and 
everyone else would probably follow suit.

John

At 09:26 AM 6/30/2006, Doug Schaefer wrote:
>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


Back to the top