Bernd Fondermann wrote:
I am with you regarding jdk, ant, maven.
But JUnit is a not a build tool like ant + maven, it is a bunch of java
classes our code directly dependents on (is linked to) through
import-statements. this is true for all other libraries in lib and
tools/lib. (do you want them be removed, too?) JDK classes are also
linked by import statements, but the junit.jar is a little bit more
lightweight ;-)
We should not impose additional hurdles for users by requiring them to
download stuff before the tests can be run.
Remember, the same applied to activation.jar and mail.jar. They had to
be downloaded, extracted and placed by hand. They are now present in the
repository and this is a great relief, I think.
Bernd
The problem is that junit, in the "ant build" aspect, is not a
dependency of James but a dependency of the ant-junit task.
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.
Maven2 is a step beyond in that because it automatically downloads
"taskdefs" (maven plugins) and their dependencies.
Maven2 will also create a build.xml that automcatically downloads the
dependencies using the get task, but it will skip junit.jar because of
the limitation I already described.
PS: We still don't include activation and mail jars in our repository.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
