[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jdt-core-dev] CompilationUnit outside classpath - second warning
|
Resending due to mail problems.
----- Forwarded by Philippe Mulet/SNZ/OTI on 10/29/2002 11:25 AM -----
|---------+---------------------------->
| | Philippe Mulet |
| | |
| | 10/28/2002 12:31 |
| | PM |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: jdt-ui-dev@xxxxxxxxxxx, jdt-debug-dev@xxxxxxxxxxx |
| cc: jdt-core-dev@xxxxxxxxxxx |
| Subject: [jdt-core-dev] CompilationUnit outside classpath - second warning |
>---------------------------------------------------------------------------------------------------------------------------------------------|
If we get no further argument on this front, we will release the new
behavior in tomorrow's integration build.
i.e. only working copies will be usable on units defined outside the
classpath (compilation units will fail opening and existency check).
----- Forwarded by Philippe Mulet/SNZ/OTI on 10/28/2002 12:27 PM -----
|---------+------------------------------>
| | "Philippe Mulet" |
| | <Philippe_Mulet@oti|
| | .com> |
| | Sent by: |
| | jdt-core-dev-admin@|
| | eclipse.org |
| | |
| | |
| | 10/22/2002 11:51 AM|
| | Please respond to |
| | jdt-core-dev |
| | |
|---------+------------------------------>
>---------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: jdt-core-dev@xxxxxxxxxxx |
| cc: jdt-ui-dev@xxxxxxxxxxx, jdt-debug-dev@xxxxxxxxxxx |
| Subject: [jdt-core-dev] CompilationUnit outside classpath |
>---------------------------------------------------------------------------------------------------------------------------------------------|
Currently the JavaModel tolerates managing units residing outside the
project classpath. As long as the corresponding resource exists, it will
pretend it exists, it can be opened and introspected.
This was intended to provide some minimal model support for such units,
which users could drag'n drop outside/back inside the project classpath.
However, this appears to be problematic since these elements are never
closed (unless client explicitly request it to be closed), and thus these
elements will leave in our element cache for ever...
This leak cannot be solved correctly, and we propose to instead prevent
opening such elements completely. We would only preserve existing behavior
for working copies (which are sharing the same ability), and for which the
closing is automatically done at the end of its life cycle.
Please shout if you don't agree with this resolution, we are currently
planning to implement these changes by 2.1-M3.
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev
