This makes sense to me if
1) the samples are standalone Java programs (not requiring JUnit)
2) all the necessary executable files needed to run them are
present in the binary distro. For src/main files, these are
currently in the jar file. For src/test files that should not
be included in the jar (the extension samples follow this
pattern), we would need to include .class files, which isn't
happening currently.
3) the simple java -cp command is listed in the readme so that
it can be cut-and-pasted and doesn't need ant any or maven
build script to be run
It does not make sense to me if
1) The samples depend on JUnit. This means that they need more than
a simple java -cp to run them.
2) A build step using ant or maven is needed to create any of the
binary files that are needed to run the samples. This is the case
in the last binary distro that I downloaded.
3) The java -cp command (or commmands if we support different
flavours to run from either jars or classes) is buried inside
an ant or maven build script.
Simon
ant elder wrote:
On 5/11/07, Simon Laws <[EMAIL PROTECTED]> wrote:
<snip/>
4. Don't ship pre-built jars for the samples. With mvn and ant scripts
> provided for all the samples, it's really easy for anyone to build
> the necessary class and jar files themselves.
I'm happy to ditch them and there is a very tiny change to the ant build
if
they are not there.
I really like having the pre-built samples in the binary distro and the
simplicity they provide by being able to run them out-of-the-box with a
simple java -cp command. What is the problem with keeping them?
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
