Bernd Fondermann wrote:
The problem is that junit, in the "ant build" aspect, is not a dependency of James but a dependency of the ant-junit task.

I am not sure that I understand this sentence.

For me, junit is a jar like any jar in lib/ except that it is needed only in the test classes and thus resides in tools/lib but could very well be in lib/. I see the unit test classes as an integral part of the sources, not just an add-on, even if they don't ship in binary distributions.

Our tests depends on junit: we can automatically download the junit.jar and build the tests, this is not a problem.

The problem is when you want to run the "junit" task from ant: this is an ant limitation, and this is why I would like to use something that does not present this problems (m2).

If you can find a simple solution for that I would be happy to include it: I pasted the "<get>" code, and as I said there is a classpath issue.

Agreed, the downloading is not a solution as long as we are using ant. I tried this myself a few weeks ago. Isn't this "only" a license issue? If we could put junit into svn we would do it, wouldn't we?

For the current state it is only a license issue.
Btw I still would like to remove all the jars from the repository one day (the way we did for jspf project).

Since we can't put junit in anyway the whole discussion is somewhat academic.

What I'd really like to understand more: What is the benefit of removing ant and the build scripts? Is it just a clean-up or is there a next step after it? Sorry to re-iterate this topic. I feel like I don't see the obvious here.

I have ant installed in my machine and already including junit.jar. If I remove the whole ant stuff but build.xml I'm able to run "ant run-unit-tests" without downloading/moving anything. If I keep the ant stuff in the tools/lib folder then ant expects to find junit.jar in the same folder and does not work (I have to manually copy the jar).

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to