Vladimir R. Bossicard wrote:
Nope. JUnit is required to *test* Xindice, which is a developer-only concern. Users don't give a damn about unit tests, developers do, so by shipping Junit you are shipping a component that user will never use. Tests can (and should, IMHO) be an optional part in the user-oriented build process.
AFAIK the tests are compiled when you compile Xindice.
Which is dead wrong from a user POV. They could be easily made optional.
But again, I don't really care about Junit being part of the repo, I have absolutely no problem in having a live CVS where things change, evolve and mutate in an Open Source spirit, you seem to have one.
I think that the added value for developers of unit tests running automatically fully justify the inclusion of Junit in CVS (even if it should be noted that every serious java developer had a working junit on her classpath).
I think that the added value for users of having a smooth build process fully justifies the inclusion of Ant in CVS (even if, again, every java developer has her copy of Ant).
I think that the added value for users of having a server running the "1.0" way, seamlessly and easily, and for developers of having a compile-test-run cycle integrated with the ability of run unit tests against XML-RPC calls, fully justifies the inclusion of Jetty.
All in all, I have no taliban principles to defend: I think that good Open Source software comes from bubbling repositories, ruled by evolution itself rather then principles. CVS should be a playground (true, with some rules, as every playground) rather then a sanctuary.
But again, it's just MHO (luckily, however, I don't feel alone).
Ciao,
-- Gianugo
