Package | Description |
---|---|
org.netbeans.api.project |
General API for finding and manipulating all kinds of projects.
|
org.netbeans.spi.project |
Support for defining project types.
|
org.netbeans.spi.project.support |
ProjectAPI
The Project API defines abstract projects, i.e. groupings of files built and
manipulated as units. It is used for Ant-based projects but could support
other scenarios such as makefiles. Modules can plug in project types which can
recognize certain folders as being projects, and define their behaviors.
Besides the visible Javadoc, this module permits a project to add implementations
of org.netbeans.spi.queries.FileBuiltQueryImplementation
,
org.netbeans.spi.queries.SharabilityQueryImplementation
and
org.netbeans.spi.queries.FileEncodingQueryImplementation
into the project lookup (rather than global lookup).
The implementations will be consulted only in the case the relevant file
belongs to that project (according to org.netbeans.api.project.FileOwnerQuery
).
This helps avoid the need to consult irrelevant query implementations.
ProjectIconAnnotator
A mechanism for changing the project node icon. You can use it for example to add a badge to the project's icon.
MoveOrRenameOperationImplementation
Extended interface giving projects the ability to implement a simple display name change more safely and efficiently.
CacheDirectoryProvider
Added ProjectUtils.getCacheDirectory
to complement
the SPI interface CacheDirectoryProvider
.
SourceGroupModifier
provides ways of create specific folders (SourceGroup
root folders)
in case they don't exist, eg. cannot be retrieved from Sources
.
The project supporting automated creation of SourceGroup root folders needs to
provide SourceGroupModifierImplementation
in the project's lookup.
@ProjectServiceProvider
and @LookupMerger.Registration
Added annotations to register entries to project lookup individually.
These can be used instead of implementing a LookupProvider
.
Since the entries are loaded on demand, this can help avoid needless class loading.
The SPI should be used by modules defining particular project types, e.g. the J2SE project type. The API is to be used primarily by GUI infrastructure and some queries, though other module code may on occasion need to refer to the API.
Read more about the implementation in the answers to architecture questions.
Built on March 18 2014. | Portions Copyright 1997-2014 Sun Microsystems, Inc. All rights reserved.