RE: Compile error

Hal <[email protected]>
Newsgroups gmane.comp.java.smartfrog.devel
Message-ID <20050906073353008.00000001948@Hellblazer>
Either you're not compiling with a 1.4 compiler, or you're not using the 1.4+ language features (I think it's -source 1.4).

> -----Original Message-----
> From: smartfrog-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org [mailto:smartfrog-
> developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Haavard Bjerke
> Sent: Tuesday, September 06, 2005 6:53 AM
> To: smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Cc: [email protected]
> Subject: [Smartfrog-developer] Compile error
> 
> I'm just getting started making my own component for setting up Xen VMs
> with
> Smartfrog. I've followed the tutorial paper, and I get this compile error:
> 
> /opt/SmartFrog.3.06.016rc2/src/org/smartfrog/sfcore/logging/LogFactory.jav
> a:191:
> warning: as of release 1.4, assert is a keyword, and may not be used as an
> identifier
>             assert log!=null;
>             ^
> /opt/SmartFrog.3.06.016rc2/src/org/smartfrog/sfcore/logging/LogFactory.jav
> a:191:
> ';' expected
>             assert log!=null;
>                       ^
> /opt/SmartFrog.3.06.016rc2/src/org/smartfrog/sfcore/logging/LogFactory.jav
> a:191:
> cannot resolve symbol
> symbol  : class assert
> location: class org.smartfrog.sfcore.logging.LogFactory
>             assert log!=null;
>             ^
> ...
> 
> 
> The very simple source code is attached. How can I solve this problem?
> 
> Thanks,
> Havard
> 



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.