62a4ae05ab
element will have to be change. this is an example of the differences in testing patterns. The FooBarTestCase.java used in beanutils provides a nice way to grab on to the tests while leaving test classes out of the picture while not having to explicitly write a TestAll running. So with the introduction of a nice pattern that is used in Bean utils you don't need a runner and test classes will be ommitted and you can just add test cases and go, no need to modify anything else. PR: Obtained from: Submitted by: Reviewed by: git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/collections/trunk@130749 13f79535-47bb-0310-9956-ffa450edef68 |
||
---|---|---|
data/test | ||
src | ||
.cvsignore | ||
DEVELOPERS-GUIDE.html | ||
LICENSE | ||
PROPOSAL.html | ||
README.txt | ||
RELEASE-NOTES-2.0.html | ||
STATUS.html | ||
build.properties.sample | ||
build.xml | ||
maven.xml | ||
project.xml |
README.txt
Jakarta Commons Collections =========================== Welcome to the Collections component of the Jakarta Commons project. This component requires the excellent Ant utility. It can be found here : http://jakarta.apache.org/ant/ For testing the project, you will also need JUnit : http://www.junit.org/ To let the test process find JUnit, you may make a copy of the build.properties.sample file, rename to build.properties, and modify to reflect the location of the junit.jar on your computer. Once you have Ant propertly installed, and the build.properties file correctly reflects the location of your junit.jar, you are ready to build and test. To compile and test the component : $ ant test To build a jar : $ ant dist-jar To build the API documentation : $ ant doc To build the jar and API doc at once : $ ant dist