[jdom-interest] Anything else for beta 9?

[Bradley S. Huffman]

I got this message on this Solaris box until I modified build.sh and put
./lib/junit.jar in the LOCALCLASSPATH. But now I get a "cann't fork" on
line 237 of build.xml.

Brad

Jason Hunter writes:

> > >OK, I've integrated all the comments from the build testing.  Looking
> > >good.  Only open issue left is the "build testui" problem.  Seems like a
> > >JUnit class loader thing?
> > 
> > Hmm, maybe this is the same problem I'm seeing. Currently I have four
> > failures in TestElement (not just in testui but also in plain test)
> > all related to the missing Element.addContent(CDATA) method. Is that
> > what you're seeing? Could be a JUnit class loader issue but I can't
> > explain it. I would really feel a lot more comfortable if all the
> > tests were passing.
> 
> I'm hitting a different problem.  My "build test" runs aren't working at
> all ever since I upgraded to JUnit 3.8.1.  Ant complains it can't find
> the <junit> task.  It's strange because "build testui" and "build
> testreport" work fine.  I was happy to see "build testui" run with a
> green bar, so I checked in the new JUnit.  Strange "build test" would
> break.  Anyone have ideas?
> 
> Here's the output:
> 
> C:\cvs\cvs.jdom.org\jdom-test>build test
> Building...
> Building with classpath c:\jdk1.4.0\lib\tools.jar;..\jdom\lib\ant.jar;
> ..\jdom\lib\xml-apis.jar;..\jdom\lib\xerces.jar;.\lib\optional.jar;
> Starting Ant...
> Buildfile: build.xml
> 
> ... etc ...
> 
> test:
> 
> BUILD FAILED
> file:C:/cvs/cvs.jdom.org/jdom-test/build.xml:239: Could not create task
> or type
> of type: junit.
> 
> Ant could not find the task or a class this task relies upon.
> 
> This is common and has a number of causes; the usual
> solutions are to read the manual pages then download and
> install needed JAR files, or fix the build file:
>  - You have misspelt 'junit'.
>    Fix: check your spelling.
>  - The task needs an external JAR file to execute
>    and this is not found at the right place in the classpath.
>    Fix: check the documentation for dependencies.
>    Fix: declare the task.
>  - The task is an Ant optional task and optional.jar is absent
>    Fix: look for optional.jar in ANT_HOME/lib, download if needed
>  - The task was not built into optional.jar as dependent
>    libraries were not found at build time.
>    Fix: look in the JAR to verify, then rebuild with the needed
>    libraries, or download a release version from apache.org
>  - The build file was written for a later version of Ant
>    Fix: upgrade to at least the latest release version of Ant
>  - The task is not an Ant core or optional task
>    and needs to be declared using <taskdef>.
> 
> Remember that for JAR files to be visible to Ant tasks implemented
> in ANT_HOME/lib, the files must be in the same directory or on the
> classpath
> 
> Please neither file bug reports on this problem, nor email the
> Ant mailing lists, until all of these causes have been explored,
> as this is not an Ant bug.
> 
> Total time: 2 seconds
> 
> C:\cvs\cvs.jdom.org\jdom-test>
> _______________________________________________
> To control your jdom-interest membership:
> http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost
> .com
>