[news.eclipse.tools] Re: Rigid project directory structure?

["Philippe Mulet" <philippe_mulet@xxxxxxx>]

Eclipse is managing resources located inside its workspace (listening to
changes etc...).
The workspace itself can contain remote projects (i.e. not defined inside
the workspace location). But beyond this, all further resources (your actual
folders and files) have to be contained inside the project folders.

This is a limitation, there are requests logged against Platform/Core in
order to improve this (but this is not on the 2.0 plan).
However, if you check http://bugs.eclipse.org/bugs/show_bug.cgi?id=6664,
you'll notice some suggestions on how to work-around this
by using symlinks.

"Silvio Bierman" <sbierman@xxxxxxxx> wrote in message
news:a8ud9b$s08$1@xxxxxxxxxxxxxxxx
> Hello All,
>
> I have been using JBuilder and Netbeans until now. In our company we
mainly
> develop servlet-based applications and we usually put the IDE projects in
> the web-application-directory, setting the output directory to
> WEB-INF/classes. We have multiple web-application directories, but we
> maintain a single tree of Java sources which we do not want to pollute
with
> IDE-specific project files.
>
> This is where we are running into problems now we are cnsidering a move to
> Eclipse. We want to keep working this way, but Eclipse does not allow
> mounting source directories to a project when the directory is not located
> beneath the project directory. Why is Eclipse so rigid in this area?
What's
> wrong with the way JBuilder, Netbeas and J++ allow us to mount any old
> directory to the project?
>
> Any thoughts?
>
> Kind regards,
>
> Silvio Bierman
>
>