Issue 'TRQS4' has just been modified by user '[EMAIL PROTECTED]'

You can view the issue detail at the following URL:
     <http://scarab.werken.com/issues/id/TRQS4>

The following modifications were made to this issue:

Martin pointed out on IRC that my original patch caused the maven runtime:test goal to 
fail.  It turned out that maven was using one naming convention for torque properties 
(the right one) and the ant files (and a number of other places) were all screwed up.  
This made for a more invasive patch, but now all but a couple of the property names 
are correct.  I tweaked build-test.xml to stick everything in the same place as maven 
runtime:test.  While maven runtime:test completes successfully (exactly the same as 
prior to this patch) executing build-test.xml produces cleaner output from some of the 
tasks.

Note that I have corrected jmcnally.profile, but this should perhaps be left to John.

I have also included the change to the test-runtime target of build-test.xml that 
executes any test cases that are found so TRQS3 can go in straight on the back of this 
patch.  Note that I did not make this same change in the copy of build-test.xml in the 
src/rttest directory - this file doesn't appear to be used.  




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

Reply via email to