Package org.aspectj.org.eclipse.jdt.core
Schnittstelle IJavaModelMarker
public interface IJavaModelMarker
Markers used by the Java model.
This interface declares constants only.
-
Feldübersicht
Modifizierer und TypFeldBeschreibungstatic final String
Id marker attribute (value"arguments"
).static final String
Build path problem marker type (value"org.aspectj.org.eclipse.jdt.core.buildpath_problem"
).static final String
ID category marker attribute (value"categoryId"
)static final String
Classpath file format marker attribute (value"classpathFileFormat"
).static final String
Cycle detected marker attribute (value"cycleDetected"
).static final String
Flags marker attribute (value"flags"
).static final String
ID marker attribute (value"id"
).static final String
Java model problem marker type (value"org.eclipse.jdt.core.problem"
).static final String
Output overlapping another source attribute (value"outputOverlappingSource"
).static final String
Java model task marker type (value"org.eclipse.jdt.core.task"
).static final String
Java model transient problem marker type (value"org.aspectj.org.eclipse.jdt.core.transient_problem"
).
-
Felddetails
-
JAVA_MODEL_PROBLEM_MARKER
Java model problem marker type (value"org.eclipse.jdt.core.problem"
). This can be used to recognize those markers in the workspace that flag problems detected by the Java tooling during compilation.- Siehe auch:
-
TRANSIENT_PROBLEM
Java model transient problem marker type (value"org.aspectj.org.eclipse.jdt.core.transient_problem"
). This can be used to recognize those markers in the workspace that flag transient problems detected by the Java tooling (such as a problem detected by the outliner, or a problem detected during a code completion). Since 1.0, transient problems are reported asIProblem
through various API. Only the evaluation API is still producing markers for transient problems.- Siehe auch:
-
TASK_MARKER
Java model task marker type (value"org.eclipse.jdt.core.task"
). This can be used to recognize task markers in the workspace that correspond to tasks specified in Java source comments and detected during compilation (for example, 'TO-DO: ...'). Tasks are identified by a task tag, which can be customized throughJavaCore
option"org.aspectj.org.eclipse.jdt.core.compiler.taskTag"
.- Seit:
- 2.1
- Siehe auch:
-
ARGUMENTS
Id marker attribute (value"arguments"
). Arguments are concatenated into one String, prefixed with an argument count (followed with colon separator) and separated with '#' characters. For example: { "foo", "bar" } is encoded as "2:foo#bar", { } is encoded as "0:".Empty argument is encoded as three spaces (" ").
If the argument contains a '#', the character is doubled.
{"foo#test", "bar" } is encoded as "2:foo##test#bar"- Seit:
- 2.0
- Siehe auch:
-
ID
ID marker attribute (value"id"
).- Siehe auch:
-
CATEGORY_ID
ID category marker attribute (value"categoryId"
)- Seit:
- 3.2
- Siehe auch:
-
FLAGS
Flags marker attribute (value"flags"
). Reserved for future use.- Siehe auch:
-
CYCLE_DETECTED
Cycle detected marker attribute (value"cycleDetected"
). Used only on buildpath problem markers. The value of this attribute is either "true" or "false".- Siehe auch:
-
BUILDPATH_PROBLEM_MARKER
Build path problem marker type (value"org.aspectj.org.eclipse.jdt.core.buildpath_problem"
). This can be used to recognize those markers in the workspace that flag problems detected by the Java tooling during classpath setting.- Siehe auch:
-
CLASSPATH_FILE_FORMAT
Classpath file format marker attribute (value"classpathFileFormat"
). Used only on buildpath problem markers. The value of this attribute is either "true" or "false".- Seit:
- 2.0
- Siehe auch:
-
OUTPUT_OVERLAPPING_SOURCE
Output overlapping another source attribute (value"outputOverlappingSource"
). Used only on buildpath problem markers. The value of this attribute is either "true" or "false".- Seit:
- 3.6.4
- Siehe auch:
-