asfimport
commented
19 years ago cutting@apache.org (@cutting) (migrated from JIRA)
I think the plan (correct me if I'm wrong) is to fold the most useful of the sandbox items into the standard Lucene build tree when Lucene's code is moved to a top-level project. They'll still be packaged into separate jar file(s).
Once this happens, javadocs could either be built in a separate tree, or, perhaps better yet, put them in separate javadoc group(s):
http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html#group
For example, Nutch uses groups to separate the Core APIs from plugins:
This isn't something i think is crucial, but since i've been on the lucene-users mailing list (less then 2 months) I've seen several people post questions asking where they can find documentation on some module available in the sandbox.
the answer of course is usually that they should download the source and build the javadocs themselves, but since it keeps coming up, I figured i'd suggest setting up a nightly "build" of the whole sandbox, including the javadocs.
if nothing else, it will cut down on the number of questions – but i think it may also have an added benefit to the size of the user base. In my experience, people tend to be more willing to download/install something and try it out after they've read the docs online.
Migrated from LUCENE-332 by Hoss Man (Legacy Bugzilla Account), 1 vote, resolved Feb 28 2006 Environment: