[news.eclipse.tools] Re: Can anyone tell me why the output path must be

["Sherif" <sherif_issa@xxxxxxxxx>]

Thanks for your response. I think having eclipse supporting resources
outside the workspace is a good idea. This will allow me, at least, to limit
a java project to a subset of my directory tree. From my own experience most
of my company's projects start from src, also our classes are under src,
src/classes, so if I want to map my source code to src I will get all the
projects we have. Kind of too much for one project. What I would like to
have is to create one project say src/xxx and have its output classes go to
src/classes.

S.


"Philippe Mulet" <philippe_mulet@xxxxxxx> wrote in message
news:a4aoce$2vn$1@xxxxxxxxxxxxxxxx
> Eclipse resources have to live inside projects, and generated classfiles
are
> just another kind of resources produced by the Java builder.
> In order projects to see changed in generated classfiles (incremental
> recompilation), it is necessary that these be true resources.
>
> If Eclipse was supporting folders outside a project to be true managed
> resources (like projects living outside the workspace location) then the
> Java limitation could disappear. So please enter a motivated bug report
> against Platform/Core if you need this behavior to change.
>
>
> "Sherif" <sherif_issa@xxxxxxxxx> wrote in message
> news:a4a4jv$t5a$1@xxxxxxxxxxxxxxxx
> > I think this is kind of limiting. decoupling the two paths can make
> projects
> > much flexible.
> >
> > S.
> >
> >
>
>