james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <n...@devtech.com>
Subject RE: [DISCUSSION] Include Unit Tests in regular build
Date Sat, 11 Nov 2006 19:17:46 GMT
>>>>   ant run-unit-test -Dtest=org.apache.james.smtpserver.SMTPServerTest
>>> I think that generally speaking it is not a good idea to complicate the
>>> build.xml with unused targets
>> And why is this bad, as opposed to the `mvn test -Dtest=SMTPServerTest`,
>> which you just suggested?  And why would it be unused?
> You instead proposed to change our build.xml (if I understood you).
> This is different, isn't it?

A trivial change to build.xml vs adopting Maven?  Oh yes, very different.
:-)  Ant lets me do what I want, with a little effort.  Maven lets you do
what they want, with no effort at all.  ;-)

It was a trivial, one-time, change to build.xml.  I've just commited it
after testing it.  Sample below.

	--- Noel

  $ ant run-unit-test -Dtest=SMTPServerTest
  Buildfile: build.xml
  [...]
  compile-unit-tests:
       [echo] Compiling James Unit Test Java sources

  ensure-test-name:

  run-unit-test:
      [echo] Running A Single James Unit Test
      [junit] Running org.apache.james.smtpserver.SMTPServerTest
      [junit] Tests run: 42, Failures: 0, Errors: 0, Time elapsed: 9.959 sec
  [...]
  BUILD SUCCESSFUL
  Total time: 21 seconds



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message