Links from tests to production classes

Question

Our source tree has two top-level branches: one for test and the other for production classes. The package (subdirectory) structure is identical in both branches. This is, I believe a fairly common arrangement. However, it creates a problem with Javadoc that I haven't been able to solve. I want to build documentation collections separately for the two branches, so that the test and production classes aren't commingled. If I do this, I get warnings about @link references not being found wherever the documentation of a test class links to the documentation of a production class, even though they are in the same package. I've tried various solutions: "-link"ing to the production documentation, including both branches of the source tree in the source path and naming the test classes (rather than the packages) on the command line, etc. Nothing gives me the results I want.
Given how common (I believe) this organization is--to the extent that it's supported by some IDEs--I'm surprised I can't get Javadoc to do what I want. Am I missing something, or is this really not possible?

Answer 1

I've tried that. It doesn't work.I assume you have the sources for one package split across two source locations. Have just tried this under Windows with jdk 1.5.0_06 and 1.4.2_10 and they both seem to allow this.
Created this class file in src1\p1\Reg.java
package p1;
public class Reg {
     * Does something
    public void doit(){
        System.println("done it");
}And created this class file in src2\p1\Reg2.java
package p1;
public class Reg2 extends Reg {
     * The main
    public static void main(String[] args){
        new Reg2().doit();
}And then ran the command:
javadoc -sourcepath "./src1;./src2" p1I get one set of documentation that includes both classes with links between them, but no errors.