WASdev/standards.jsr352.jbatch — pull request #7 by BrentDouglas (2014-10-19 20:29:45+00:00)
Title: Re-add sigtest and downloadable zip to build; Run TCK in build

Firstly, this is based on https://github.com/WASdev/standards.jsr352.jbatch/pull/3 so
please look at that before this one.

- Delete some eclipse config files. They didn't look important, everything
can be run through maven now.
- Delete no longer used build.xml from tck module. It wasn't hooked up
to maven so far as I could see anyhow.
- Add sigtest generation to tck modules pom. It was in the build.xml
that was removed. These are not enabled by default as the JDK
locations must be specified in a properties file and are enabled
individually in build profiles. README.md has been updated with
the details.
- Add batch.xml generation to tck modules pom. It was also in the build.xml
that was removed.
- Update module com.ibm.jbatch.tck to build a jar that contains all the
files nessessary to execute the TCK using the maven-dependency-plugin
unpack goal, a common way of executing test's in third party jars. This will
be a huge win for other implementations that might want to check their build
against the tck. This is not currently possible as the [tck jar in central](http://repo1.maven.org/maven2/com/ibm/jbatch/com.ibm.jbatch-tck/1.0/com.ibm.jbatch-tck-1.0.jar)
doesn't contain the tests, the job.xml files or batch.xml.
- Add module com.ibm.jbatch.tck.dist to build the downloadable zip. This is
needed to allow adding a dependency on the javadoc and sources jars of
the tck module.
- Add module com.ibm.jbatch.tck.exec to execute the tck with the RI. This is
not strictly necessary but IMO it makes it simpler to just run unpack in the
test-classes directory knowing it will be empty and not going to overwrite
any unit tests.

This might cause some merge conflicts with some of the other PR's, of so
let me know when you merge them and I will rebase it.