How to improve jde-junit.el to meet the suggested test file location guidelines listed in the junit faq?

At my current employer, we follow the guidelines laid out in the junit faq, but jde-junit.el wants to put junit test implementations in the same directory as the java object implementation to be tested.

To my untrained eye, it would seem that a new custom variable for a working directory should be created and it should be referenced by jde-junit-add-test-to-suite-internal but i lack the skills to implement the changes to jde-junit-add-test-to-suite-internal (assuming that i am correct as to where the change should be made :-) )

I note with interest the following jde mail that was evidently never implemented:

http://www.mail-archive.com/[email protected]/msg07822.html

"This command will also use a customization variable that I plan to
implement named,

  jde-junit-test-case-directory"


Is this something that's kicking around on a harddrive somewhere and not checked in?

tnx in advance for any help you can provide!

johnu

PS:

Here is the JUnit FAQ entry that outlines a suggested structure:

http://junit.sourceforge.net/doc/faq/faq.htm#organize_1

Organizing Tests

   1.

      Where should I put my test files?

      You can place your tests in the same package and directory as the classes under test.

      For example:

          src
             com
                xyz
                   SomeClass.java
                   SomeClassTest.java	 
                

      While adequate for small projects, many developers feel that this approach clutters the source directory, and makes it hard to package up client deliverables without also including unwanted test code, or writing unnecessarily complex packaging tasks.

      An arguably better way is to place the tests in a separate parallel directory structure with package alignment.

      For example:

          src
             com
                xyz
                   SomeClass.java
          test
             com
                xyz
                   SomeClassTest.java	 
                

      These approaches allow the tests to access to all the public and package visible methods of the classes under test.