[jdt-ui-dev] Re: CompilationUnit outside classpath

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jdt-ui-dev] Re: CompilationUnit outside classpath - second warning

From: "Adam Kiezun" <Adam_Kiezun@xxxxxxx>
Date: Tue, 29 Oct 2002 11:36:08 +0100
Delivered-to: jdt-ui-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/pipermail/jdt-ui-dev/>
List-help: <mailto:jdt-ui-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev>, <mailto:jdt-ui-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/listinfo/jdt-ui-dev>, <mailto:jdt-ui-dev-request@eclipse.org?subject=unsubscribe>

i guess our code is not ready for it and will be hurt.

i have 2 questions:
1. do we only need to change from getUnderlyingResource  to getResource for ICompilationUnits?

2. and if not, then is it ok to change all getUnderlyingResource calls to getResource calls?

a.

References:
- [jdt-ui-dev] [jdt-core-dev] CompilationUnit outside classpath - second warning
  - From: Philippe Mulet

Prev by Date: [jdt-ui-dev] [jdt-core-dev] CompilationUnit outside classpath - second warning
Next by Date: Re: [jdt-ui-dev] Re: CompilationUnit outside classpath - second warning
Previous by thread: [jdt-ui-dev] [jdt-core-dev] CompilationUnit outside classpath - second warning
Next by thread: Re: [jdt-ui-dev] Re: CompilationUnit outside classpath - second warning
Index(es):
- Date
- Thread

Breadcrumbs