Markers themselves are handles in the same way as IResources
are handles. Instances of IMarker
do not hold the attributes themselves but rather uniquely refer to the attribute container. As such, their state may change underneath the handle with no warning to the holder of the handle.
Each marker has:
"org.eclipse.core.resources.taskmarker"
), The resources plug-in defines five standard types:
org.eclipse.core.resources.marker
org.eclipse.core.resources.taskmarker
org.eclipse.core.resources.problemmarker
org.eclipse.core.resources.bookmark
org.eclipse.core.resources.textmarker
org.eclipse.core.resources.markers
) into which other plug-ins can install marker type declaration extensions. Marker types are declared within a multiple inheritance type system. New markers are defined in the plugin.xml
file of the declaring plug-in. A valid declaration contains elements as defined by the extension point DTD:
All markers declared as persistent
are saved when the workspace is saved, except those explicitly set as transient (the TRANSIENT
attribute is set as true
). A plug-in which defines a persistent marker is not directly involved in saving and restoring the marker. Markers are not under version and configuration management, and cannot be shared via VCM repositories.
This interface is not intended to be implemented by developers.
Markers implement the IAdaptable
interface; extensions are managed by the platform's adapter manager.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|