At 08:50 AM 9/5/2005, Philip wrote:
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?
I tried for a while to find something online too.. The best I could do is
this <http://www.mail-archive.com/[email protected]/msg16092.html>.
here again is an example of the error I'm getting:
<http://csdl.ics.hawaii.edu/~kagawaa/replace-error.txt>.
Can you create a small build.xml that exhibits the problem that we can use
to document this?
You can't really reproduce this error without generating the javareport
html files. So, the best thing to do is upgrade to Java 5 and Ant 1.6.5 (by
the way, this fails in Ant 1.6.4 ant Ant 1.6.2) then running "ant -version
freshStart junitAll". The fact that the error occurs in Ant 1.6.5, 1.6.4,
and 1.6.2, could mean that its a Java5 bug and not a Ant bug. I'm using
this java5 version:
c:\java\cvs\hackyBuild>java -version
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)
Note that I upgraded both my laptop and desktop and I get this error on
both. I've asked Honbing to confirm on his local machine.
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...
- 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?
Here are some warning examples in Eclipse
<http://csdl.ics.hawaii.edu/~kagawaa/eclipse-warnings.txt>.
- 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?
Actually, the most of the Eclipse warnings are the same warnings the
compiler provides. Here is a link to a file:
<http://csdl.ics.hawaii.edu/~kagawaa/compile-warnings.txt>. You can see
that there is 100 warnings in hackyKernel alone. Oh, you have to add a
"compilearg" in the javac task to see these warnings. Here is an example
from the hackyKernel/local.build.xml
<javac srcdir="${src.dir}"
destdir="${install.war.web-inf.classes.dir}"
debug="on">
<compilerarg value="-Xlint"/>
<classpath refid="compile.classpath"/>
</javac>
thanks, aaron
