The default classpath problem should be fixed by http:// issues.apache.org/jira/browse/HADOOP-700.

Along with the contrib javadoc, do you also want the example javadoc mixed in with the api docs as it currently is? In my mind, the examples pollute the "All Known Implementing Classes" and "Direct Known Subclasses" sections of the api javadoc.

The site docs are not currently included in the release tar file. I've filed http://issues.apache.org/jira/browse/HADOOP-744 to capture this bug. I like the redirect idea for a top-level index.html.


On Nov 22, 2006, at 10:41 AM, Doug Cutting (JIRA) wrote:

[ http://issues.apache.org/jira/browse/HADOOP-371? page=comments#action_12452011 ]

Doug Cutting commented on HADOOP-371:
-------------------------------------

I believe smallJobsBenchmark was initially placed in contrib to keep it in a separate jar, not on the default classpath. So wherever it is moved, it should retain that property.

I would prefer putting the contrib javadoc together with the main javadoc, as is done in Lucene:

http://lucene.apache.org/java/docs/api/overview-summary.html

As for a top-level index.html, should that really differ from site/ index.html? That's included in releases and links to everything you mention, I think. Perhaps we should simply add an index.html with a meta-redirect to that page. Lucene does this:

http://svn.apache.org/viewvc/lucene/java/trunk/index.html?view=markup

(Like the last-modified date on that one?)


ant tar should package contrib jars
-----------------------------------

                Key: HADOOP-371
                URL: http://issues.apache.org/jira/browse/HADOOP-371
            Project: Hadoop
         Issue Type: Improvement
           Reporter: Michel Tourn
        Attachments: build.tarcontrib.patch, contribbuild.patch


From Hadoop-356:
I note that the contrib packages are not included in distributions (the "tar" target). They probably should be. Michel, would you like to modify "tar" to include the contrib code?
This should be done in a separate bug.
OK.
This packaging is done in target deploy-contrib.
So I can just add a dependency to the top-level tar target:
<!-- Make release tarball (s) -->
<target name="tar" depends="package, deploy-contrib">

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/ Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/ software/jira



Reply via email to