Project API
Official

ProjectAPI The Project API defines abstract projects, i.e.

See:
Description

Project API

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.

What is New (see all changes)?

• Oct 5 '06 Added support for composing project's lookup from multiple sources.

  Added interfaces and support classes that can be used to compose the project's lookup from multiple 3rd party sources. Framework for creating merged instances included. LookupMerger implementation for Sources added.

• Sep 8 '06 Added support for project configurations

  Added an interface ProjectConfigurationProvider which can be included in a project's lookup to support switchable configurations / profiles.

• Aug 22 '05 Added support for project delete/copy/rename/move

  Introduced: New method notifyDeleted added to ProjectState. Interfaces DataFilesProviderImplementation, DeleteOperationImplementation, CopyOperationImplementation, MoveOperationImplementation has been added to support project delete/copy/rename/move. Support class ProjectOperations has been added to simplify operations on compound projects.

• May 27 '05 The FileOwnerQuery.markExternalOwner allows registration of individal files and URIs

  It is possible to register owner of an individual file using FileOwnerQuery.markExternalOwner. It is possible to register owner of a folder or file using URI, so the folder or file does not have to exist at the time of registration.

• Dec 22 '04 Switched to major release version 1

  To indicate that this is now considered a stable API, the major release version was incremented to 1 from 0.

Use Cases

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.

Exported Interfaces

This table lists all of the module exported APIs with defined stability classifications. It is generated based on answers to questions about the architecture of the module. Read them all...

Group of java interfaces

Interface Name	In/Out	Stability	Specified in What Document?
ProjectAPI	Exported	Official	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.

Implementation Details

What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?

Nothing.

Read more about the implementation in the answers to architecture questions.