The question is, what is going to happen
in Eclipse 3.3 for Europa, for which we’re targeting CDT 4.0. I know it’s
early to predict what will happen in 3.3, but I think everyone is assuming that
the flood gates will open. I’ll make it a topic at the Callisto beers
today. J.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Niefer
Sent: Friday, June 30, 2006 11:01
AM
To: CDT
General developers list.
Subject: RE: [cdt-dev] HEAD is
broken
Only the bundles that specify 1.5 are built with 1.5. The
JRE used to compile is configured on a per-bundle basis.
See
the new help docs in 3.2 : Plug-in Development Environment Guide > Tasks
> Advanced PDE Build topics > Controlling Compilation Environment.
-Andrew
Chris
Recoskie/Toronto/IBM@IBMCA
Sent
by: cdt-dev-bounces@xxxxxxxxxxx
06/30/2006 10:49 AM
Please
respond to
"CDT General developers list."
<cdt-dev@xxxxxxxxxxx>
|
|
To
|
"CDT General
developers list." <cdt-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
RE: [cdt-dev] HEAD is broken
|
|
I
think though that they build using the 1.5 compiler in 1.4.2
compatibility mode. If you turn off
compatibiIity mode, it could still
blow up. I could be wrong though, maybe
they're doing full 1.5 builds now.
===========================
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:43 RE: [cdt-dev] HEAD is broken
AM
Please
respond to
"CDT General
developers list."
<cdt-dev@eclipse.
org>
The Eclipse Platform is built with 1.5. I use 1.5
every day and have no
problems. I think the issue is the Platform
starting to use 1.5 features
which would force people to move to 1.5.
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:38 AM
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
_______________________________________________
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