|RE: [wtp-dev] Compile failures due to change inClasspathDependencyUtil?|
From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Thursday, December 13, 2007 11:42 AM
Subject: [wtp-dev] Compile failures due to change inClasspathDependencyUtil?
And Rob !?
It appears the "getDefaultRuntimePath(boolean)" method recently changed to "getDefaultRuntimePath(boolean, boolean)"
Is this a "breaking API change"? Is it required for adopters to react? Should there be too methods, one with old signature which assumes the other boolean is true or false and calls the old version? I would assume we should have the two versions, but haven't looked at why the change was made.
Source File: org/eclipse/jst/jsf/core/internal/project/facet/JSFFacetInstallDelegate.java
1. ERROR: ParameterMismatch
The method getDefaultRuntimePath(boolean, boolean) in the type ClasspathDependencyUtil is not applicable for the arguments (boolean)
176 : ClasspathDependencyUtil.getDefaultRuntimePath(true).toString());
Back to the top