This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 150209 - Update API javadoc pages for 6.5
Summary: Update API javadoc pages for 6.5
Status: RESOLVED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-15 12:26 UTC by Jaroslav Tulach
Modified: 2008-11-07 03:09 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2008-10-15 12:26:34 UTC
Someone from platform team needs to update javadoc for 6.5. There used some items in checklist, but the checklist is 
gone, as far as I can tell (there is a broken link at http://platform.netbeans.org/guidelines/index.html)

But looking into the history:
http://web.archive.org/web/20080115182217/http://www.netbeans.org/community/guidelines/checklist.html
I can see at least these tasks:

nbbuild/build.properties (daily-alpha-nbms and javadoc module configurations). javadoc shall contain only modules that 
provide at least one stable or official api and are included in the release

nbbuild/javadoctools/export2html.xsl (change the HTML header part to talk about appropriate version and possibly say 
that all apis are available at the dev URL: http://www.netbeans.org/download/dev/javadoc/) 

nbbuild/build.properties (needs to contain proper information about the date of previous version, so in trunk version 
update the values of previous.version properties to match the date of creating the branch)
Comment 1 Jesse Glick 2008-10-17 23:04:41 UTC
I think Yarda has historically taken care of this. At least I do not remember ever doing it. Probably some involvement
from the web team is needed too?
Comment 2 Jaroslav Tulach 2008-10-20 12:32:28 UTC
Mark, how do you plan to handle this task?
Comment 3 Antonin Nebuzelsky 2008-10-20 12:56:07 UTC
> Mark, how do you plan to handle this task?

Mark is not taking care of Platform API pages.

Jardo, what did you do the last time you took care of that? You did that for 6.1.

6.1 APIs are available on a separate URL:
http://bits.netbeans.org/6.1/javadoc/

Was changing the three properties you mentioned above enough?

Reassigning to random people without providing more details is not a way transfer of a task should be done.
Comment 4 Jaroslav Tulach 2008-10-20 17:43:32 UTC
1. This used to be the checklist: 
http://web.archive.org/web/20080115182217/http://www.netbeans.org/community/guidelines/checklist.html

2. If there is some newer one, without appropriate related info, I'd be glad to provide the howto.

3. the three properties not enough. There are is more, as described in #1.

4. Mark promised me 1/2 year ago, he would take this task out of my responsibility. As such I feel authorized to have 
assigned this issue to Mark.

Comment 5 Antonin Nebuzelsky 2008-10-21 17:14:08 UTC
Jirko, take this one.
Comment 6 Jiri Rechtacek 2008-10-22 11:01:59 UTC
Javadoc pages changes for trunk: http://hg.netbeans.org/core-main/rev/74ad1531c12f
Javadoc pages changes for trunk: http://hg.netbeans.org/release65/rev/65cd9e9a5b1c
RE team can generate Javadoc for 6.5 now. I'll ask them for this.
Comment 7 Quality Engineering 2008-10-22 15:43:02 UTC
Integrated into 'main-golden', will be available in build *200810221401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/74ad1531c12f
User: Jiri Rechtacek <jrechtacek@netbeans.org>
Log: #150209: Update API javadoc pages for Dev
Comment 8 Jiri Rechtacek 2008-10-30 10:58:06 UTC
fixed wrong heading in Apichanges: http://hg.netbeans.org/release65/rev/43d5ac3f3993
Btw. RE team still hasn't uploaded NetBeans 6.5 Javadoc yet although I was asking for it for several times.
Comment 9 Jesse Glick 2008-11-07 03:09:16 UTC
Probably the currently recommended process should be published in wiki.