|
Eclipse JDT 2.1 |
|||||||||
PREV NEXT | FRAMES NO FRAMES |
Deprecated Classes | |
org.eclipse.jdt.ui.JavaElementContentProvider
use the StandardJavaElementContentProvider instead |
Deprecated Interfaces | |
org.eclipse.jdt.core.util.IClassFileDisassembler
- should use ClassFileBytesDisassembler instead |
|
org.eclipse.jdt.core.ICodeCompletionRequestor
Use an ICompletionRequestor instead |
Deprecated Methods | |
org.eclipse.jdt.core.ICodeAssist.codeComplete(int, ICodeCompletionRequestor)
- use codeComplete(int, ICompletionRequestor) instead |
|
org.eclipse.jdt.core.eval.IEvaluationContext.codeComplete(String, int, ICodeCompletionRequestor)
- use codeComplete(String, int, ICompletionRequestor) instead |
|
org.eclipse.jdt.core.ToolFactory.createDefaultClassFileDisassembler()
- should use factory method creating ClassFileBytesDisassembler instead |
|
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.createInheritedMethods(IType, boolean, boolean, IImportsStructure, IProgressMonitor)
Use createInheritedMethods(IType,boolean,boolean,IImportsManager,IProgressMonitor) |
|
org.eclipse.jdt.core.search.SearchEngine.createJavaSearchScope(IResource[])
Use createJavaSearchScope(IJavaElement[]) instead |
|
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.createTypeMembers(IType, IImportsStructure, IProgressMonitor)
Overwrite createTypeMembers(IType, IImportsManager, IProgressMonitor) instead |
|
org.eclipse.jdt.debug.eval.IEvaluationResult.getErrors()
use getErrorMessages() |
|
org.eclipse.jdt.debug.eval.ICompiledExpression.getErrors()
use getErrorMessages() |
|
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.getFileComment(ICompilationUnit)
Instead of file templates, the new type code template specifies the stub for a compilation unit. |
|
org.eclipse.jdt.debug.core.IJavaExceptionBreakpoint.getFilters()
Use getExclusionFilters() or getInclusionFilters() |
|
org.eclipse.jdt.ui.ITypeHierarchyViewPart.getInput()
use getInputElement instead |
|
org.eclipse.jdt.core.dom.Statement.getLeadingComment()
This feature was removed in the 2.1 release because it was only a partial, and inadequate, solution to the issue of associating comments with statements. Furthermore, AST.parseCompilationUnit did not associate leading comments, making this moot. Clients that need to access comments preceding a statement should use a scanner to reanalyze the source text immediately preceding the statement's source range. |
|
org.eclipse.jdt.core.IJavaProject.getPackageFragmentRoots(IClasspathEntry)
Use IJavaProject#findPackageFragmentRoots instead |
|
org.eclipse.jdt.core.IClasspathEntry.getResolvedEntry()
- use JavaCore.getResolvedClasspathEntry(...) |
|
org.eclipse.jdt.core.dom.Message.getSourcePosition()
Use getStartPosition() instead. |
|
org.eclipse.jdt.core.IJavaModelStatus.getString()
Use IStatus#getMessage instead |
|
org.eclipse.jdt.ui.wizards.NewTypeWizardPage.getTemplate(String, ICompilationUnit)
Use getTemplate(String,ICompilationUnit,int) |
|
org.eclipse.jdt.core.search.IJavaSearchScope.includesBinaries()
Use SearchEngine.createJavaSearchScope(IJavaElement[]) with the package fragment roots that correspond to the binaries instead |
|
org.eclipse.jdt.core.search.IJavaSearchScope.includesClasspaths()
Use SearchEngine.createJavaSearchScope(IJavaElement[]) with a java project instead |
|
org.eclipse.jdt.debug.core.IJavaExceptionBreakpoint.isInclusiveFiltered()
Exception breakpoints can have a mixed set of filters and this method is maintained strictly for API backwards compatibility |
|
org.eclipse.jdt.core.JavaConventions.isOverlappingRoots(IPath, IPath)
Overlapping roots are allowed in 2.1 |
|
org.eclipse.jdt.ui.JavaElementSorter.isSorterProperty(Object, Object)
Bug 22518. Method never used: does not override ViewerSorter#isSorterProperty(Object, String). Method could be removed, but kept for API compatibility. |
|
org.eclipse.jdt.ui.jarpackager.JarPackageData.logErrors()
will be removed in final 2.0 |
|
org.eclipse.jdt.ui.jarpackager.JarPackageData.logWarnings()
will be removed in final 2.0 |
|
org.eclipse.jdt.core.JavaCore.removeClasspathVariable(String)
- use version with extra IProgressMonitor |
|
org.eclipse.jdt.ui.JavaUI.revealInEditor(IEditorPart, ISourceReference)
use revealInEditor(IEditorPart, IJavaElement) instead |
|
org.eclipse.jdt.core.JavaCore.setClasspathVariable(String, IPath)
- use API with IProgressMonitor |
|
org.eclipse.jdt.debug.core.IJavaExceptionBreakpoint.setFilters(String[], boolean)
Exception breakpoints can have a mixed set of filters. Use setInclusiveFilters(String[] filters) or setExclusiveFilters(String[] filters) |
|
org.eclipse.jdt.core.search.IJavaSearchScope.setIncludesBinaries(boolean)
Use SearchEngine.createJavaSearchScope(IJavaElement[]) with the package fragment roots that correspond to the binaries instead |
|
org.eclipse.jdt.core.search.IJavaSearchScope.setIncludesClasspaths(boolean)
Use SearchEngine.createJavaSearchScope(IJavaElement[]) with a java project instead |
|
org.eclipse.jdt.ui.ITypeHierarchyViewPart.setInput(IType)
use setInputElement instead |
|
org.eclipse.jdt.core.dom.Statement.setLeadingComment(String)
This feature was removed in the 2.1 release because it was only a partial, and inadequate, solution to the issue of associating comments with statements. |
|
org.eclipse.jdt.ui.jarpackager.JarPackageData.setLogErrors(boolean)
will be removed in final 2.0 |
|
org.eclipse.jdt.ui.jarpackager.JarPackageData.setLogWarnings(boolean)
will be removed in final 2.0 |
|
Eclipse JDT 2.1 |
|||||||||
PREV NEXT | FRAMES NO FRAMES |