Four development stages (or levels of quality) are recognized:
No*- if that kind of content does not exist at all
Stub*- if only short placeholder exists
Draft*- if something is unfinished (regardless of how much)
Complete*- if that kind of content is finished (default)
The following kinds of content have predefined annotation types:
*Api- APIs, i.e. signature and semantics of public types and members
*Code- implementation code, i.e. all code behind APIs
*Tests- tests, usually unit tests
*Docs- javadoc, perhaps also external docs (presumably linked from the javadoc)
There is no
NoCode annotation, because it has no meaning and
StubCode annotation should be used in its place instead. Applications/libraries are free to define their own annotation types, but the above listed ones are expected to be supported by scanning tools.
Nuances in meaning can be clarified in string parameter that is taken by all annotations. Specific issues are however better described with
*Issue annotations, which can be repeated and thus provide more space for detailed descriptions.
Annotations have the default retention
RetentionPolicy.CLASS. Tools can scan for these annotations in sources, during annotation processing, and in compiled class files. Annotations also show up in javadoc for annotated code, so that users are informed about development stage of the class/method they are using.
- See Also:
- Stagean homepage
Annotation Types Summary Annotation Type Description ApiIssueDescription of one API issue. ApiIssuesCollection of
CodeIssueDescription of one code issue. CodeIssuesCollection of
CompleteApiOptionally flags code that has finished API. CompleteCodeOptionally flags code that has finished implementation. CompleteDocsOptionally flags code that has finished javadoc. CompleteTestsOptionally flags code that has finished tests. DocIssueDescription of one documentation issue. DocIssuesCollection of
DraftApiFlags code that has unfinished API. DraftCodeFlags code that has unfinished implementation. DraftDocsFlags code that has unfinished javadoc. DraftTestsFlags code that has unfinished tests. NoApiFlags code that does not have any public API at all. NoDocsFlags code that does not have any javadoc at all. NoTestsFlags code that does not have any tests at all. StubApiFlags code that has almost no API. StubCodeFlags code that has almost no implementation. StubDocsFlags code that has almost no javadoc. StubTestsFlags code that has almost no tests. TestIssueDescription of one test issue. TestIssuesCollection of