You can use tags <usecase name="name> regular html description </usecase>
and if you want to use an URL you can prefix if with @TOP@ to begin
at the root of your javadoc
</hint>
Describe the main <a href="http://wiki.netbeans.org/API_Design#The_Importance_of_Being_Use_Case_Oriented">
use cases</a> of the new API. Who will use it under
what circumstances? What kind of code would typically need to be written
to use the module?
</question>
-->
<answerid="arch-usecases">
<p>
XXX no answer for arch-usecases
</p>
</answer>
<!--
<question id="arch-what" when="init">
What is this project good for?
<hint>
Please provide here a few lines describing the project,
what problem it should solve, provide links to documentation,
specifications, etc.
</hint>
</question>
-->
<answerid="arch-what">
<p>
XXX no answer for arch-what
</p>
</answer>
<!--
<question id="arch-where" when="impl">
Where one can find sources for your module?
<hint>
Please provide link to the Hg web client at
http://hg.netbeans.org/
or just use tag defaultanswer generate='here'
</hint>
</question>
-->
<answerid="arch-where">
<defaultanswergenerate='here' />
</answer>
<!--
<question id="compat-deprecation" when="init">
How the introduction of your project influences functionality
provided by previous version of the product?
<hint>
If you are planning to deprecate/remove/change any existing APIs,
list them here accompanied with the reason explaining why you
are doing so.
</hint>
</question>
-->
<answerid="compat-deprecation">
<p>
XXX no answer for compat-deprecation
</p>
</answer>
<!--
<question id="compat-i18n" when="impl">
Is your module correctly internationalized?
<hint>
Correct internationalization means that it obeys instructions
at <a href="http://www.netbeans.org/download/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/i18n-branding.html">
NetBeans I18N pages</a>.
</hint>
</question>
-->
<answerid="compat-i18n">
<p>
XXX no answer for compat-i18n
</p>
</answer>
<!--
<question id="compat-standards" when="init">
Does the module implement or define any standards? Is the
implementation exact or does it deviate somehow?
</question>
-->
<answerid="compat-standards">
<p>
XXX no answer for compat-standards
</p>
</answer>
<!--
<question id="compat-version" when="impl">
Can your module coexist with earlier and future
versions of itself? Can you correctly read all old settings? Will future
versions be able to read your current settings? Can you read
or politely ignore settings stored by a future version?
<hint>
Very helpful for reading settings is to store version number
there, so future versions can decide whether how to read/convert
the settings and older versions can ignore the new ones.
</hint>
</question>
-->
<answerid="compat-version">
<p>
XXX no answer for compat-version
</p>
</answer>
<!--
<question id="dep-jre" when="final">
Which version of JRE do you need (1.2, 1.3, 1.4, etc.)?
<hint>
It is expected that if your module runs on 1.x that it will run
on 1.x+1 if no, state that please. Also describe here cases where
you run different code on different versions of JRE and why.
</hint>
</question>
-->
<answerid="dep-jre">
<p>
XXX no answer for dep-jre
</p>
</answer>
<!--
<question id="dep-jrejdk" when="final">
Do you require the JDK or is the JRE enough?
</question>
-->
<answerid="dep-jrejdk">
<p>
XXX no answer for dep-jrejdk
</p>
</answer>
<!--
<question id="dep-nb" when="init">
What other NetBeans projects and modules does this one depend on?
<hint>
Depending on other NetBeans projects influnces the ability of
users of your work to customize their own branded version of
NetBeans by enabling and disabling some modules. Too
much dependencies restrict this kind of customization. If that
is your case, then you may want to split your functionality into
pieces of autoload, eager and regular modules which can be
enabled independently. Usually the answer to this question
is generated from your <code>project.xml</code> file, but
if it is not guessed correctly, you can suppress it by
specifying <defaultanswer generate="none"/> and
write here your own. Please describe such projects as imported APIs using
the <code><api name="identification" type="import or export" category="stable" url="where is the description" /></code>.
By doing this information gets listed in the summary page of your
javadoc.
</hint>
</question>
-->
<answerid="dep-nb">
<defaultanswergenerate='here' />
</answer>
<!--
<question id="dep-non-nb" when="init">
What other projects outside NetBeans does this one depend on?
<hint>
Depending on 3rd party libraries is always problematic,
especially if they are not open source, as that complicates
the licensing scheme of NetBeans. Please enumerate your
external dependencies here, so it is correctly understood since
the begining what are the legal implications of your project.
Also please note that
some non-NetBeans projects are packaged as NetBeans modules
(see <a href="http://libs.netbeans.org/">libraries</a>) and
it is preferred to use this approach when more modules may
depend and share such third-party libraries.
</hint>
</question>
-->
<answerid="dep-non-nb">
<p>
XXX no answer for dep-non-nb
</p>
</answer>
<!--
<question id="dep-platform" when="init">
On which platforms does your module run? Does it run in the same
way on each?
<hint>
If you plan any dependency on OS or any usage of native code,
please describe why you are doing so and describe how you envision
to enforce the portability of your code.
Please note that there is a support for <a href="http://www.netbeans.org/download/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/api.html#how-os-specific">OS conditionally
enabled modules</a> which together with autoload/eager modules
can allow you to enable to provide the best OS aware support
on certain OSes while providing compatibility bridge on the not
supported ones.
Also please list the supported
OSes/HW platforms and mentioned the lovest version of JDK required
for your project to run on. Also state whether JRE is enough or
you really need JDK.
</hint>
</question>
-->
<answerid="dep-platform">
<p>
XXX no answer for dep-platform
</p>
</answer>
<!--
<question id="deploy-dependencies" when="final">
What do other modules need to do to declare a dependency on this one,
in addition to or instead of the normal module dependency declaration
(e.g. tokens to require)?
<hint>
Provide a sample of the actual lines you would add to a module manifest
to declare a dependency, for example OpenIDE-Module-Requires: some.token.
If other modules should not depend on this module, or should just use a
simple regular module dependency, you can just answer "nothing". If you
intentionally expose a semistable API to clients using implementation
dependencies, you should mention that here (but there is no need to give
an example of usage).
</hint>
</question>
-->
<answerid="deploy-dependencies">
<p>
XXX no answer for deploy-dependencies
</p>
</answer>
<!--
<question id="deploy-jar" when="impl">
Do you deploy just module JAR file(s) or other files as well?
<hint>
Usually a module consist of one JAR file (perhaps with Class-Path
extensions) and also a configuration file that enables it. If you