[jdt-core-dev] Behavior change for getUnderlyingResource() and getCorres

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

[jdt-core-dev] Behavior change for getUnderlyingResource() and getCorrespondingResource()

From: "Jerome Lanneluc" <Jerome_Lanneluc@xxxxxxx>
Date: Mon, 21 Oct 2002 17:05:38 +0200
Delivered-to: jdt-core-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/pipermail/jdt-core-dev/>
List-help: <mailto:jdt-core-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/jdt-core-dev>, <mailto:jdt-core-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/listinfo/jdt-core-dev>, <mailto:jdt-core-dev-request@eclipse.org?subject=unsubscribe>

The next integration build will contain a fix for
http://bugs.eclipse.org/bugs/show_bug.cgi?id=25041

As the spec says, a JavaModelException is now thrown when calling
getUnderlyingResource() and getCorrespondingResource() on an IJavaElement
that doesn't exist.

Clients that need to get the resource handle of an IJavaElement that does
not exist should use IJavaElement.getResource().

Jerome

Prev by Date: [jdt-core-dev] We should put bug IDs in comment area when releasing changes
Next by Date: Re[4]: [jdt-core-dev] Re: What should Eclipse compiler default settings be ?
Previous by thread: [jdt-core-dev] We should put bug IDs in comment area when releasing changes
Next by thread: [jdt-core-dev] CompilationUnit outside classpath
Index(es):
- Date
- Thread

Breadcrumbs