[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] "assert" in cdt source vs. java compiler versions i nprojects
|
Despite popular belief, from what I've seen from the traffic, most people
are still working on the 4.0.x stream, where we are still 1.4 compliant.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Mike Kucera
> Sent: Tuesday, December 11, 2007 11:07 AM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] "assert" in cdt source vs. java compiler versions
> inprojects
>
> Why are we even having this discussion, shouldn't we have moved to Java 5
> by now?
>
> Mike Kucera
> Software Developer
> IBM CDT Team, Toronto
> mkucera@xxxxxxxxxx
>
>
>
>
> "Schorn, Markus"
> <Markus.Schorn@wi
> ndriver.com> To
> Sent by: "CDT General developers list."
> cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
> clipse.org cc
>
> Subject
> 12/11/2007 04:59 RE: [cdt-dev] "assert" in cdt
> AM source vs. java compiler versions
> inprojects
>
> Please respond to
> "CDT General
> developers list."
> <cdt-dev@eclipse.
> org>
>
>
>
>
>
>
> Hi,
> The plugins can certainly be compiled for java 1.4. However the
> sources are not 1.3 compatible.
>
> When obtaining the projects for the plugins from the CVS repository,
> these settings are defined correctly. (compiler-compliance=1.4,
> source-compatibility=1.4)
>
> How do you create the projects before you build them? Do you use the
> builder
> provided by JDT or the ant-build provided by PDE?
>
> Markus.
>
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Don Porges
> Sent: Monday, December 10, 2007 6:13 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] "assert" in cdt source vs. java compiler versions
> inprojects
> Importance: Low
>
>
> Every time I try to build the CDT from source, as I did again this week
> from the 4.0.2 update, I run into the same thing that has to be tweaked:
> 3 of the plugins use the Java "assert" statement but have the java
> compiler version explicitly set to 1.4 in the project properties, which
> implies source compatibility with 1.3, which does not know about that
> keyword. The
> 3 plugins are:
>
> org.eclipse.cdt.core
> org.eclipse.cdt.refactoring
> org.eclipse.cdt.ui
>
> In order to build these in the workbench, I have to change the Java
> compiler version in each project to 5.0. And then, if I want to export
> them from the workbench, I have to change the version again, this time
> in build.properties. It's certainly possible that my workflow is
> different from the way that the real developers do it, but I don't
> understand how anybody ever builds these plugins without changing the
> project settings. My installed java is Sun's 1.6.0, on Windows XP, if
> that makes a difference.
>
> --
> View this message in context:
> http://www.nabble.com/%22assert%22-in-cdt-source-vs.-java-compiler-versi
> ons-in-projects-tp14182576p14182576.html
> Sent from the Eclipse CDT - Development mailing list archive at
> Nabble.com.
>
> _______________________________________________
> 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
