[ BUILD # : 200409220845 ]
[ JDK VERSION : J2SE 1.4.2 ]

When in freeform project properties, lists of
sources, classpath and output directories can be
entered.

Also, with classpath and output entries, there is
a choice to enter global values or to enter values
against each source directory.

In the same way, there should be the capability to
enter javadoc directories (I suppose with the same
choice of global or against each source directory).  

The javadoc directories specified in this manner
would act in the same way as javadoc directories
attached to libraries used in normal projects:
they would appear during code completion, as well
as being available for the "show javadoc" option
to access.

The javadoc that would be used in this way ranges
from:

1. pre-built javadoc from third party sources
(similar to the library scenario for normal
projects); to 
2. user-built (included in the users Ant) javadoc
generated from third party source that the user is
compiling; to 
3. user-built javadoc that is generated from the
code that is the content of the current project.

Alternatives:

1.
The first of those options could be easily
supplied by extending the library concept to
freeform projects - allowing a freeform project to
have a library attached to it allows third party
code and javadoc to be integrated into the
process, and would be independantly beneficial.
(http://www.netbeans.org/issues/show_bug.cgi?id=49769)

But this wouldn't provide the second or third
options satisfactorally

2. 
Allow freeform projects to depend on other
projects and set up a project for the appropriate
sources (working similar to alternative 1).

This could be even more confusing than alternative
1, though.  Depending on the project structure, it
could be very awkward to set up.  (this could,
however, also be independantly useful)