RE: [cdt-dev] "assert" in cdt source vs. java compiler versions inprojec

[Don Porges <dporges@xxxxxxxxxxxxxxx>]

I don't get the projects from cvs.  What I've been doing is:

Install the CDT SDK feature from the master .zip file (such as
cdt-master-4.0.2.zip)
Import-->Plugin Development-->Plugins and Fragments
Make sure that Import as "Projects with source folders" is selected
Select all CDT plugins (minus src/doc/test)
Import them.

The workbench does its building and then I get the errors I described.  The 
Preferences-->Java Compiler panel indicates compiler compliance level 1.4,
with "Use default compliance settings" checked, and therefore the source
compatibility settings are greyed out, but it indicates source compatibility
1.3.


Schorn, Markus wrote:
> 
> 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
> 
> 

-- 
View this message in context: http://www.nabble.com/%22assert%22-in-cdt-source-vs.-java-compiler-versions-in-projects-tp14182576p14276786.html
Sent from the Eclipse CDT - Development mailing list archive at Nabble.com.