[kepler-dev] [Bug 5557] Replace hardcoded path separator with File.pathSeparator

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5557

Christopher Brooks <cxh at eecs.berkeley.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
       Hours Worked|                            |1.25
                 CC|                            |cxh at eecs.berkeley.edu

--- Comment #4 from Christopher Brooks <cxh at eecs.berkeley.edu> 2012-01-09 00:01:30 PST ---
I took a look at the javadoc problem under Linux and there were a number of
problems.

- The -taglet parameter named org.kepler.build.RatingTaglet, but that class
does not exist.  I set -taglet to doc.doclets.RatingTaglet.  I'm not about
this.

- I was seeing errors like
java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast
to com.sun.javadoc.AnnotationTypeDoc

The net said that this would occur if a class had annotations but the jar file
that contained the annotations was not included in the classpath to javadoc.
So, I added ptolemy/src/lib/junit-4.8.2.jar and
ptolemy/src/lib/JUnitParams-0.3.0.jar to CreateJavadoc.  I don't understand why
I need to add these jar
files individually.  When javadoc is run, the classpath should include
all the jar files for all the modules.

I'm still getting 2 errors and a message about the subprocess returning 1
under Linux.

Under Windows, I was getting lots of warnings and beeps as well.  I believe the
problem is that the jar files are getting processed as source?  Probably the
fix is to exclude the .jar files somehow.

I've found that javadoc does not work very well with large argument strings.
Ant has a way to use files instead of large argument strings.  
I recently updated the javadoc command in ptII/build.xml.  That file is created
by running (cd $PTII;./configure).

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.