Re: IDE on Linux

["John Wells" <jb@sourceillustrated.com>]

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:

org.test.GUI
org.test.Backend

If my code is located in the following:
/home/myuser/classes/org/test/GUI
/home/myuser/classes/org/test/Backend

Eclipse will handle the above perfectly.

However, if I have:
/home/myuser/classesONE/org/test/GUI
/home/myuser/classesTWO/org/test/Backend

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.

Thanks,
John

Henri Yandell said:
>
>
> On Mon, 7 Apr 2003, Calvin Yu wrote:
>
>>
>> On Sun, 6 Apr 2003 11:02:41 -0400 (EDT), John Wells
>> <jb@sourceillustrated.com> 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