jdt

Provides JDI interfaces

Package Specification

This package provides a definition of the JDI class interfaces as specified in the JPDA. The specification for these interfaces can be found at http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdi/index.html

Provides JDI interfaces

Package Specification

This package provides a definition of the JDI class interfaces as specified in the JPDA. The specification for these interfaces can be found at http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdi/index.html

Provides JDI interfaces

Package Specification

This package provides a definition of the JDI class interfaces as specified in the JPDA. The specification for these interfaces can be found at http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdi/index.html

Provides JDI interfaces

Package Specification

This package provides a definition of the JDI class interfaces as specified in the JPDA. The specification for these interfaces can be found at http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdi/index.html

Provides JDI interfaces

Package Specification

This package provides a definition of the JDI class interfaces as specified in the JPDA. The specification for these interfaces can be found at http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdi/index.html

Note that the apt tool and its associated APIs may be changed or superseded in future j2se releases. @since 1.5

Note that the apt tool and its associated APIs may be changed or superseded in future j2se releases. @since 1.5

Note that the apt tool and its associated APIs may be changed or superseded in future j2se releases. @since 1.5

Note that the apt tool and its associated APIs may be changed or superseded in future j2se releases. @since 1.5

Package Specification

This package contains utilities for performing Java annotation processing in command-line builds and ant scripts.

Package Specification

This package contains Eclipse extensions of APIs related to the com.sun.mirror.apt.AnnotationProcessorEnvironment interface. Use these extensions in order to access features available only within Eclipse. Avoid these extensions if compatibility with Sun's apt tool is required.

Package Specification

This package contains miscellaneous utilities related to Java annotation processing, such as the APIs needed to configure the annotation processor settings and factory path.

Package Specification

This package contains the Java model classes, which implement Java specific behaviour for resources and further decompose java resources into model elements.

Package Specification

This package contains some compiler tooling APIs, allowing to perform operations at a lower-level than using the JavaModel.

Package Specification

This package contains the Java DOM/AST classes. An API for manipulating the source code of a Java program as a structured document. In particular, it provides a full abstract syntax tree for a Java compilation unit, which can be queried for resolved type information, and modified. The principal classes are {@link org.eclipse.jdt.core.dom.AST AST} {@link org.eclipse.jdt.core.dom.ASTNode ASTNode}, and {@link org.eclipse.jdt.core.dom.ASTParser ASTParser}.

Package Specification

This package contains the Java DOM/AST classes used to make changes to an existing DOM/AST tree. The principal classes are {@link org.eclipse.jdt.core.dom.rewrite.ASTRewrite ASTRewrite} and {@link org.eclipse.jdt.core.dom.rewrite.ListRewrite ListRewrite}.

Package Specification

Package Specification

This package contains classes to format Java code. The principal classes are {@link org.eclipse.jdt.core.formatter.CodeFormatter CodeFormatter} and {@link org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants DefaultCodeFormatterConstants}.

Package Specification

The JDOM was made obsolete by the addition in 2.0 of the more powerful, fine-grained DOM/AST API found in the org.eclipse.jdt.core.dom package.

Package Specification

Package Specification

Provides an implementation of a debug model based on JPDA (Java Platform Debug Architecture).

Package Specification

This package provides a set of classes and interfaces that implement a debug model based on JPDA/JDI (Java Debug Interface). It provides a set of interfaces that extend the base set of debug element interfaces to provide access to Java specific attributes and behavior. This model defines and provides utilities for creating line breakpoints, method entry breakpoints, exception breakpoints, and field watchpoints.

Provides a set classes and interfaces that support evaluations in the Java debugger.

Package Specification

This package defines a set of classes and interfaces that support evaluations in the Java debugger. Two evaluation engines are provided - one that performs evaluations by compiling and deploying class files locally for execution, and one that performs an interpretation over an abstract syntax tree. The later supports remote evaluation via JDI.

Package Specification

• Javadoc comments
• Multi-line comments
• Single-line comments

Comment Formatting

The formatting process is then launch by calling CommentRegion#format(String), where the argument denotes the desired indentation. This method returns a textedit representing the changes that where made during the formatting process. The document for which the comment region was created is therefore guaranteed to remain unchanged.

Internally, the comment region is first cast into comment lines to form the basis of the following scan step: Each comment line is scanned for valid prefixes and tokenized afterwards. This tokenize step yields a stream of tokens called comment ranges that are then marked with attributes representing information about the kind of token associated with that comment range.

Once the comment ranges have enough attributed information, the comment region wraps the comment ranges at the line margin boundary. This is coordinated by a set of rules that can be contributed to a certain type of comment region. At this point of time, the comment range stream already represents the formatted comment region. The last step therefore is to record the edits and to construct the resulting text edit, which describes all the changes that were made to the comment region.
Note that the changes are not directly applied to the document. Clients are responsible for applying the textedit and updating and preserving the document structure.

All the objects used during comment formatting should not directly be instantiated, but rather retrieved from the factory CommentObjectFactory. This factory ensures that the right kind of regions and lines are returned for a specific comment type.

Package Specification

It contains a spell-check engine specialized in Javadoc comments. Several dictionaries with Java specific content like Javadoc keywords, HTML tags and Task tags are provided. Additionally, the engine contributes correction proposals to the QuickFix processor. For non Java specific content the engine also contributes word completion proposals to the content assist processor.

Spell-check engine

Note: Locale sensitive dictionaries must be located in the "dictionaries/" subdirectory of the JDT UI plugin install location. The dictionaries are newline-separated word lists having the filename "language_country.dictionary", where "language" and "country" are the lowercase ISO-3166 language and country codes, respectively. The default dictionary is "en_us.dictionary". For correct behavior of the spell-check engine, at least the default dictionary must be installed. The default dictionary corresponds to the default locale of the spell-check engine.

Dictionaries

• A dictionary for Javadoc tags: This dictionary contains the most commonly used Javadoc tags. When spell-checking Javadoc comments, this dictionary contributes correction proposals to the QuickFix processor to correct misspelt Javadoc tags.
• A dictionary for HTML tags: This dictionary contains the most commonly used HTML tags for writing Javadoc comments. When spell-checking Javadoc- or multiline comments, this dictionary contributes correction proposals to the QuickFix processor as well as word completion proposals to the Content Assist processor.
• A dictionary for Task tags: This dictionary reflects the currently available Java Task tags. When spell-checking arbitrary text in Java files, this dictionary contributes proposals both to the QuickFix processor and the Content Assist processor.

QuickFix processor

• Proposals for correct spelling: A number of words considered most similar to the incorrectly spelt word.
• The proposal to correct the sentence capitalization: This proposal is offered on incorrectly spelt words at the beginning of a sentence.
• The proposal to add the unrecognized word to the locale-insensitive dictionaries
• The proposal to ignore the word during the current editing session

Content Assist processor

Package Specification

Spell Check Engine

The following steps are needed to obtain a spell-checker for a specific language:

• Create an instance of ISpellCheckEngine. In this package, no default implementation is provided, since the management of the dictionary registering and loading is application dependent. Usually, instances of ISpellCheckEngine are implemented as singletons.
• Create the appropriate dictionaries that should be used during the spell-check process. All dictionaries that can be registered with ISpellCheckEngine must implement the interface ISpellCheckDictionary. For this interface, an abstract implementation is provided in the class AbstractSpellDictionary. Depending on the language of the words contained in this dictionary, custom algorithms for the phonetic hash (IPhoneticHashProvider) and the edit distance (IPhoneticDistanceAlgorithm) should be implemented and registered with the dictionary.
• Instances of spell-checkers can now be created by calling createSpellChecker(Locale), where the locale denotes the language that the spell-checker should use while executing.

Dictionaries

This package provides a default implementation of a dictionary (AbstractSpellDictionary) that uses algorithms convenient for english languages.
Every dictionary needs two kinds of algorithms to be plugged in:

• An edit distance algorithm: Edit distance algorithms implement the interface IPhoneticDistanceAlgorithm. The algorithm is used to determine the similarity between two words. This package provides a default implementation for languages using the latin alphabet (DefaultPhoneticDistanceAlgorithm). The default algorithm uses the Levenshtein text edit distance.
• A hash algorithm: Phonetic hash providers implement the interface IPhoneticHashProvider. The purpose of phonetic hashes is to have a representation of words which allows comparing it to other, similar words. This package provides a default implementation which is convenient for slavic and english languages. It uses the double metaphone algorithm by published Lawrence Philips.

Spell Check Iterators

Event Handling

A spell event contains the following information:

• The word being spell-checked
• The begin index of the current word in the text medium
• The end index in the text medium
• A flag whether this word was found in one of the registered dictionaries
• A flag that indicates whether this word starts a new sentence
• The set of proposals if the word was not correctly spelt. This information is lazily computed.

Package Specification

Package Specification

Provides support for execution environments.

An execution environment describes the capabilities of a Java runtime environment, for example J2SE-1.4. This package provides facilities for contributing execution environments and providing analyzers to identify JREs as compatible with execution environments.

Package Specification

Provides support for source lookup.

These classes and interfaces have been deprecated in Eclipse 3.0. Source lookup facilities are now provided by the debug platform - see org.eclipse.debug.core.sourcelookup. Source lookup support specific to the Java debugger is now provided in org.eclipse.jdt.launching.sourcelookup.containers.

Package Specification

Package Specification

The class JavaUI is the main access point to the Java user interface components. It allows to programmatically open editors on Java elements and open package and type prompter dialogs. The package exposes constants for retrieving Java user interface parts from the workbench registry. JavaUI gives access to the IWorkingCopyManager. It manages the working copies that are in use for Java compilation units.

The interfaces ITypeHierarchyViewPart and IPackagesViewPart define the programming interface to interact with the type hierarchy and packages view parts.

The classes JavaElementContentProvider and JavaElementLabelProvider support presenting Java elements in JFace viewers.
 

Package Specification

It is recommended that clients use action groups to populate menus and tool bars instead of adding actions directly.

Clients are allowed to instantiate classes from this package. The classes are not intended to be subclassed. All actions and groups require that the selection provided by the site, view part or page passed to the action's or group's constructor is of type org.eclipse.jface.viewers.IStructuredSelection .

Package Specification

Package Specification

Package Specification

Package Specification

Clients who want to participate in Java search queries should implement IQueryParticipant. A query participant interprets a QuerySpecification and reports matches to a ISearchRequestor. If a query participant wishes to report matches against elements that are not IResources or IJavaElements, it has to implement a IMatchPresentation to render these elements.

Package Specification

Package Specification

Package Specification

Package Specification

Package Specification