| Re: [jdt-ui-dev] Re: [jdt-core-dev] CompilationUnit outside classpath |
We too have a lot of .java files outside the claspath in our test suite,
and we intend to still allow to open them in the Java editor. We just want
to allow the creation of working copies on these .java files. An
ICompilationUnit on such a .java file should not be openable.
Jerome
"Adam Kiezun"
<Adam_Kiezun@oti. To: jdt-ui-dev@xxxxxxxxxxx
com> cc:
Sent by: Subject: [jdt-ui-dev] Re: [jdt-core-dev] CompilationUnit outside classpath
jdt-ui-dev-admin@
eclipse.org
10/22/2002 12:11
PM
Please respond to
jdt-ui-dev
> 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.
if that means i won't be able to open my test resources (more than 3000
.java files outside of classpath), then i guess i'll better
shout. :)
a.
_______________________________________________
jdt-ui-dev mailing list
jdt-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev