I am wondering if we could get the best of both worlds by having
JUnit tests under sca/itest that invoke the samples (think of these
tests as "wrappers"), and removing all traces of JUnit from the
samples themselves. I'll try to do this on one or two samples and
see how well this works out.
Simon
Simon Laws wrote:
snip
I don't think the client that is used should be different
depending on whether ant or mvn was used to run the sample.
In both cases I think calculatorClient should be used.
So we would need to engineer the poms in the build to run the new client
classes rather than the junit classes. I don't think we should take the
junit tests out of the samples for the main build as the samples provide a
useful extra set of tests (although if we have to to make for a better user
experience then we have to). I'm just going to look at how the distribution
build works. Maybe we can ship a different pom for the samples. If someone
knows let us know.
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
