The new Eclipse (2.1) allows you to have multiple src folders and also multiple binary destinations for the compiled files. Would that solver your problem?
From: Jason Chambers [mailto:firstname.lastname@example.org]
Sent: Monday, April 07, 2003 6:06 PM
To: John Wells; email@example.com
Subject: Re: IDE on Linux
That's a good point John. I like to keep my JUnit tests in a different
directory but maintain the same package name to enable my tests to exercise
package friendly/default access resources. Eclipse doesn't like this so I
ended up having to mix my test cases with my application. I can live with
this thanks to the <exclude> ability of the <javac> task in Ant, however I
have yet to get the javadoc task to work in the same manner - currently,
my Javadoc contains all classes including my test cases which is confusing
to the reader.
At 08:51 AM 4/7/2003 -0400, John Wells wrote:
>In my experience, Eclipse works great for projects that root off of the
>same directory, but is a pain for projects that have class roots in
>different physical directories.
>For example, consider the following two packages:
>If my code is located in the following:
>Eclipse will handle the above perfectly.
>However, if I have:
>It becomes a real pain to get Eclipse to recognize both packages correctly
>when importing. It typically tries to shove additionally directories into
>the second package name.
>If anyone knows how to get around this behavior in Eclipse, I'd really
>appreciate a pointer. While it would be ideal that our applications all
>rooted from a common directory, we have a few large applications that do
>not follow this design.
>Henri Yandell said:
> > On Mon, 7 Apr 2003, Calvin Yu wrote:
> >> On Sun, 6 Apr 2003 11:02:41 -0400 (EDT), John Wells
> >> <firstname.lastname@example.org> wrote:
> >> >
> >> >> I asked them to determine how to set up a
> >> >> particular directory structure,
> >> >
> >> > Admittedly, this can be confusing, and it's a knock against Eclipse
> >> in my book.
> >> >
> >> One cool thing about Eclipse is that if you set up your directory
> >> structure right, you can commit it to CVS for others to use.
> >> IMHO, Eclipse is one of easier IDEs to set up. Of course, it could be
> >> because our directory structure is more suited for Eclipse wants.
> > I've found Eclipse to be great for checking out projects that are
> > already in CVS. It blows IDEA away in that respect. However, I'm finding
> > that I go back to the command line to setup a project and getting the
> > framework into CVS.
> > So I tend not to use Eclipse on tiny throwaway pieces of code. One
> > solution, which I'll get around to, is a 'Research' project :)
> > Hen