[cdt-dev] "assert" in cdt source vs. java compiler versions in projects

[Don Porges <dporges@xxxxxxxxxxxxxxx>]

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-versions-in-projects-tp14182576p14182576.html
Sent from the Eclipse CDT - Development mailing list archive at Nabble.com.