org.eclipse.jdt.core.compiler.CategorizedProblem Maven / Gradle / Ivy
Show all versions of vaadin-client-compiler-deps Show documentation
/*******************************************************************************
* Copyright (c) 2000, 2008 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Eclipse Public License v1.0
* which accompanies this distribution, and is available at
* http://www.eclipse.org/legal/epl-v10.html
*
* Contributors:
* IBM Corporation - initial API and implementation
*******************************************************************************/
package org.eclipse.jdt.core.compiler;
import org.eclipse.jdt.internal.compiler.problem.DefaultProblem;
/**
* Richer description of a Java problem, as detected by the compiler or some of the underlying
* technology reusing the compiler. With the introduction of org.eclipse.jdt.core.compiler.CompilationParticipant,
* the simpler problem interface {@link IProblem} did not carry enough information to better
* separate and categorize Java problems. In order to minimize impact on existing API, Java problems
* are still passed around as {@link IProblem}, though actual implementations should explicitly
* extend {@link CategorizedProblem}. Participants can produce their own problem definitions,
* and given these are categorized problems, they can be better handled by clients (such as user
* interface).
*
* A categorized problem provides access to:
*
* - its location (originating source file name, source position, line number),
* - its message description and a predicate to check its severity (warning or error).
* - its ID : a number identifying the very nature of this problem. All possible IDs for standard Java
* problems are listed as constants on {@link IProblem},
* - its marker type : a string identifying the problem creator. It corresponds to the marker type
* chosen if this problem was to be persisted. Standard Java problems are associated to marker
* type "org.eclipse.jdt.core.problem"),
* - its category ID : a number identifying the category this problem belongs to. All possible IDs for
* standard Java problem categories are listed in this class.
*
*
* Note: the compiler produces IProblems internally, which are turned into markers by the JavaBuilder
* so as to persist problem descriptions. This explains why there is no API allowing to reach IProblem detected
* when compiling. However, the Java problem markers carry equivalent information to IProblem, in particular
* their ID (attribute "id") is set to one of the IDs defined on this interface.
*
* Note: Standard Java problems produced by Java default tooling will be subclasses of this class. Technically, most
* API methods dealing with problems are referring to {@link IProblem} for backward compatibility reason.
* It is intended that {@link CategorizedProblem} will be subclassed for custom problem implementation when
* participating in compilation operations, so as to allow participant to contribute their own marker types, and thus
* defining their own domain specific problem/category IDs.
*
* Note: standard Java problems produced by Java default tooling will set the marker
* IMarker#SOURCE_ID attribute to
* JavaBuilder#SOURCE_ID; compiler
* participants may specify the IMarker#SOURCE_ID
* attribute of their markers by adding it to the extra marker attributes of the problems they generate;
* markers resulting from compiler participants' problems that do not have the
* IMarker#SOURCE_ID extra attribute set do not have the
* JavaBuilder#SOURCE_ID attribute set either.
*
* @since 3.2
*/
public abstract class CategorizedProblem implements IProblem {
/**
* List of standard category IDs used by Java problems, more categories will be added
* in the future.
*/
public static final int CAT_UNSPECIFIED = 0;
/** Category for problems related to buildpath */
public static final int CAT_BUILDPATH = 10;
/** Category for fatal problems related to syntax */
public static final int CAT_SYNTAX = 20;
/** Category for fatal problems in import statements */
public static final int CAT_IMPORT = 30;
/** Category for fatal problems related to types, could be addressed by some type change */
public static final int CAT_TYPE = 40;
/** Category for fatal problems related to type members, could be addressed by some field or method change */
public static final int CAT_MEMBER = 50;
/** Category for fatal problems which could not be addressed by external changes, but require an edit to be addressed */
public static final int CAT_INTERNAL = 60;
/** Category for optional problems in Javadoc */
public static final int CAT_JAVADOC = 70;
/** Category for optional problems related to coding style practices */
public static final int CAT_CODE_STYLE = 80;
/** Category for optional problems related to potential programming flaws */
public static final int CAT_POTENTIAL_PROGRAMMING_PROBLEM = 90;
/** Category for optional problems related to naming conflicts */
public static final int CAT_NAME_SHADOWING_CONFLICT = 100;
/** Category for optional problems related to deprecation */
public static final int CAT_DEPRECATION = 110;
/** Category for optional problems related to unnecessary code */
public static final int CAT_UNNECESSARY_CODE = 120;
/** Category for optional problems related to type safety in generics */
public static final int CAT_UNCHECKED_RAW = 130;
/** Category for optional problems related to internationalization of String literals */
public static final int CAT_NLS = 140;
/** Category for optional problems related to access restrictions */
public static final int CAT_RESTRICTION = 150;
/**
* Returns an integer identifying the category of this problem. Categories, like problem IDs are
* defined in the context of some marker type. Custom implementations of {@link CategorizedProblem}
* may choose arbitrary values for problem/category IDs, as long as they are associated with a different
* marker type.
* Standard Java problem markers (i.e. marker type is "org.eclipse.jdt.core.problem") carry an
* attribute "categoryId" persisting the originating problem category ID as defined by this method).
* @return id - an integer identifying the category of this problem
*/
public abstract int getCategoryID();
/**
* Returns the marker type associated to this problem, if it gets persisted into a marker by the JavaBuilder
* Standard Java problems are associated to marker type "org.eclipse.jdt.core.problem").
* Note: problem markers are expected to extend "org.eclipse.core.resources.problemmarker" marker type.
* @return the type of the marker which would be associated to the problem
*/
public abstract String getMarkerType();
/**
* Returns the names of the extra marker attributes associated to this problem when persisted into a marker
* by the JavaBuilder. Extra attributes are only optional, and are allowing client customization of generated
* markers. By default, no EXTRA attributes is persisted, and a categorized problem only persists the following attributes:
*
* -
IMarker#MESSAGE -> {@link IProblem#getMessage()}
* -
IMarker#SEVERITY -> IMarker#SEVERITY_ERROR or
* IMarker#SEVERITY_WARNING depending on {@link IProblem#isError()} or {@link IProblem#isWarning()}
* -
IJavaModelMarker#ID -> {@link IProblem#getID()}
* -
IMarker#CHAR_START -> {@link IProblem#getSourceStart()}
* -
IMarker#CHAR_END -> {@link IProblem#getSourceEnd()}
* -
IMarker#LINE_NUMBER -> {@link IProblem#getSourceLineNumber()}
* -
IJavaModelMarker#ARGUMENTS -> some String[] used to compute quickfixes
* -
IJavaModelMarker#CATEGORY_ID -> {@link CategorizedProblem#getCategoryID()}
*
* The names must be eligible for marker creation, as defined by IMarker#setAttributes(String[], Object[]),
* and there must be as many names as values according to {@link #getExtraMarkerAttributeValues()}.
* Note that extra marker attributes will be inserted after default ones (as described in {@link CategorizedProblem#getMarkerType()},
* and thus could be used to override defaults.
* @return the names of the corresponding marker attributes
*/
public String[] getExtraMarkerAttributeNames() {
return CharOperation.NO_STRINGS;
}
/**
* Returns the respective values for the extra marker attributes associated to this problem when persisted into
* a marker by the JavaBuilder. Each value must correspond to a matching attribute name, as defined by
* {@link #getExtraMarkerAttributeNames()}.
* The values must be eligible for marker creation, as defined by IMarker#setAttributes(String[], Object[])}.
* @return the values of the corresponding extra marker attributes
*/
public Object[] getExtraMarkerAttributeValues() {
return DefaultProblem.EMPTY_VALUES;
}
}