XMLC and JUnit...

Jacob Kjome <[email protected]>
Newsgroups gmane.comp.java.enhydra.xmlc
Message-ID <[email protected]>
I am planning to update XMLC in the following way unless someone objects...

1.  Remove unnecessary ant.jar and optional.jar.  If you don't have Ant 
installed on your local machine, you have no business attempting to build 
XMLC from source anyway.  Just use the binary releases.

2.  Remove JUnit jars.  The JUnit jar should be added to ANT_HOME/lib 
anyway.  Since ant already ships with optional.jar and JUnit needs to exist 
at the same classloader level as optional.jar, this is really the only 
option.  Redefining the task and adding the JUnit jar to the build.xml's 
internal classpath won't make unit tests work....at least not in recent 
versions of Ant.  Also, it doesn't seem that the junit-ext.jar is used by 
anything, so there definitely shouldn't be a problem with removing it.

3.  Modify all <junit ...> entries to have haltonfailure="no".  All build 
files currently have either "yes" or based on some condition.  The problem 
is that one just wants to run all tests, as soon as a single failure 
happens, the testing stops.  The log files store the records of failures, 
errors, and warnings.   As such, modifying all files to not halt on failure 
will make it simpler to run tests and really has no downside.

So, please speak up if you have objections to any of the above.  Otherwise, 
I'll commit this later today.

Jake
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.