Bug 724641 (BRMS-549) - Please include API Javadoc, as had previously been provided
Summary: Please include API Javadoc, as had previously been provided
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-549
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Documentation
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Len DiMaggio
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-02 15:02 UTC by Rick Wagner
Modified: 2011-03-02 19:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
All
Last Closed: 2011-03-01 16:52:35 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-549 0 None None None Never

Description Rick Wagner 2011-02-02 15:02:46 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006HCqHIAW&sfdc.override=1
Steps to Reproduce: 1.  View downloads for 5.0.1.  Note the JavaDoc.  
2.  View downloads for 5.1.0.  Note lack of JavaDoc.

securitylevel_name: Public

We previously provided API JavaDoc, but do not provide it for BRMS 5.1.0.  Please make it available.
Comment 1 Matt Davis 2011-02-07 15:06:30 UTC 
https://c.na7.visual.force.com/apex/Case_View?id=500A0000003hSqo&sfdc.override=1
Comment 4 Julian Coleman 2011-03-01 10:57:21 UTC 
The javadocs zip has been created.
Comment 5 Julian Coleman 2011-03-01 10:57:21 UTC 
Release Notes Docs Status: Added: Not Required
Labels: Removed: needs_doc
Comment 6 Len DiMaggio 2011-03-01 16:52:35 UTC 
Verified in the docs here: 

http://jawa05.englab.brq.redhat.com/released/BRMS-5.1.0/brms-5.1.0-javadocs.zip
Comment 7 Anne-Louise Tangring 2011-03-02 19:40:48 UTC 
javadocs now available on the customer portal.
Note You need to log in before you can comment on or make changes to this bug.