with decent names is generated (link to come)
o made all the projects use a LICENSE.txt file. one this doesn't wig
out windows users and the checkstyle report likes to have one to
make sure that all sources files have a license present so if they
don't it can be reported.
o using the reactor tag in its first forms to provide a mechanism
to build the entire commons (still problems with detecting
JDK 1.4) and to generate a site where the navigation is gleaned
from the project themselves and don't have to kept in sync
manually.
o added a little front-end site deployer.
PR:
Obtained from:
Submitted by:
Reviewed by:
git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/collections/trunk@130751 13f79535-47bb-0310-9956-ffa450edef68
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