--On Thursday, September 1, 2005 11:19 PM -1000 Aaron Kagawa
<[EMAIL PROTECTED]> wrote:
Hey Guys,
An update on the very slow progress of the Java5 upgrade..
I think it's going extremely well!
- Ant Replace Task - used to replace the admin key in junit html files.
After trying with no luck, I can't seem to find a solution for the
problem with the Replace task. I've read a couple of mailing lists that
say there was a bug in 1.6.2 with replacing in Windows. Anyway, the
problem still exists that the replace task (version 1.6.5) works with
Java 1.4 and not Java 1.5. Solution: unknown. We still need this
functionality though.
Aaron, I just perused the Ant bugzilla database, and was unable to find a
bug report associated with this. Can you create a small build.xml that
exhibits the problem that we can use to document this?
If it hasn't been noticed yet, then we need to post it to ensure it gets
dealt with for an upcoming release of Ant. That's the real solution.
- Unit Tests.. after commenting out that replace task in the
build.utils.xml, I was able to run all the unit tests successfully (with
the exception of the current unit test failure for the Build Sensor
Installer code).
Excellent!
- In Eclipse 3.1 and with Java5 there are a couple hundred warnings. For
example, "local variable never read". Essentially, it is a local variable
that doesn't do anything. There are a couple of other warning types that
I had to disable in Eclipse. Not to mention, the newest version
Checkstyle just disabled a check for local variables!
We need to upgrade the Eclipse-related code to work with Eclipse 3.1.
Rather than disable warnings, it's best to actually fix the code. :-)
Takuya, will you be able to take of this, or should we have someone else
work on it?
- 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.
Can you provide examples (or a link to a file with them) so we can see what
they are?
Eclipse 3.1 Issue:
- Known Issue with Jupiter and possibly the Jupiter Sensor in Eclipse
3.1. Unfortunately, the unit tests still pass. Upon some investigation
it seems that Jupiter uses 3.1 jar files and both hackyEclipse and
hackyJupiter have 3.0 jar files. Not sure what that means. Also, some
of the 3.0 jar files in hackyEclipse and hackyJupiter are redundant.
Logged in Jira as:
<http://hackydev.ics.hawaii.edu:8080/browse/HACK-316>
Takuya, can you take a look at this?
Cheers,
Philip
