Hi Aaron,

Thanks for all your efforts.  As your reward, I've just put you back on 
csdl-local-l. :-)

--On Tuesday, September 06, 2005 11:55 PM -1000 Aaron Kagawa <[EMAIL 
PROTECTED]> wrote:

Basically, I've spent way too much time trying to figure out this problem.  For 
the
time being, I'm planning on moving on and just comment out this line...

Which line would need to be commented out?

- In Eclipse 3.1 and with Java5 there are a couple hundred warnings.

I took a look, and the warnings seem to fall into one of the following three 
categories:

1. Private fields/methods that are not used. In most (but perhaps not all) cases, the warning identifies vestigial code that we can delete.

2. Unchecked operations on collection classes. With Java 1.5, we have generics, which means we can do compile-time type declaration on Collections and get compile-time checking. Of course, to do this we have to use 1.5-specific features and leave 1.4 behind. Once we move to 1.5, we can start working on these warnings.

3. Serializable classes do not declare serialVersionUID. This is a mistake we should fix at some point, although the only place we actually serialize data right now is on the client-side when we can't connect to a server and we need to save out data until we can connect.

All in all, these are not too problematic.

To eliminate these warnings under jdk 1.5, javac has a command line option -source (i.e. 'javac -source "1.4"'). Ant 1.6.5 provides a 'source' attribute to the <javac> task. What we should do is:

- require all developers to upgrade to Ant 1.6.5
- edit the <javac> target in all local.build.xml files to include 
'source="1.4"'.

However, I suggest we refrain from this until we get the Version 6.7 stable release out the door.

We need to upgrade the Eclipse-related code to work with Eclipse 3.1.
Here are some warning examples in Eclipse
<http://csdl.ics.hawaii.edu/~kagawaa/eclipse-warnings.txt>.

It looks to me like these warnings are more to do with the Java 1.5 issues above than with Eclipse 3.1. However, we do have documented problems with the Eclipse and Jupiter sensors under Eclipse 3.1:

<http://hackydev.ics.hawaii.edu:8080/browse/HACK-314>
<http://hackydev.ics.hawaii.edu:8080/browse/HACK-316>

I still have received no communication from Takuya about his availability to work on this.


- I haven't started hacking build.xml code to conditionally build
Hackystat with Java 1.4 or Java 1.5. - Of course many compile warnings
still exist.

I think the best approach is for us all to upgrade to Ant 1.6.5 and introduce the 'source' attribute in all of the calls to <javac>. I've put this into Jira for version 6.8 at:
<http://hackydev.ics.hawaii.edu:8080/browse/HACK-324>

If we get 6.7 out this Friday, then we can do this upgrade next week.

Cheers,
Philip

Reply via email to