Bug 792949 (JBEPP-27) - productize portlet bridge documentation
Summary: productize portlet bridge documentation
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-27
Product: JBoss Enterprise Portal Platform 4
Classification: JBoss
Component: docs-Portlet_Bridge_Overview
Version: 4.3.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3.0.GA
Assignee: Scott Mumford
QA Contact: ecs-bugs
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On: JBEPP-3
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-08 21:04 UTC by Prabhat Jha
Modified: 2012-02-28 16:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-16 03:44:32 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-27 0 None Closed productize portlet bridge documentation 2012-02-16 23:13:58 UTC

Description Prabhat Jha 2008-12-08 21:04:05 UTC
Date of First Response: 2008-12-17 22:54:52
project_key: JBEPP

Josh,

Another document but a bit smaller document to productize. Current doc for Portlet Bridge is at https://svn.jboss.org/repos/portletbridge/trunk/docs/. Can you please assign a resource for this? The resulting document should be uploaded to https://svn.jboss.org/repos/portal/docs/enterprise/trunk/PortletBridge.

Comment 1 Prabhat Jha 2008-12-08 21:04:24 UTC
Link: Added: This issue depends JBEPP-3


Comment 2 Prabhat Jha 2008-12-08 21:07:02 UTC
For Section 2.2 and 2.3, please add an "eye catching" warning that "This feature is a technology preview. Hence it's not a supported feature"

Comment 3 Scott Radvan 2008-12-18 03:54:52 UTC
Uploaded...

Comments/edits welcome.

Comment 4 Thomas Heute 2009-01-05 13:06:36 UTC
It's 3.2 and 3.3 that should be marked as Tech preview, not 2.3

Comment 5 Prabhat Jha 2009-01-07 19:08:11 UTC
This has been fixed.

Comment 6 Scott Radvan 2012-02-16 22:41:20 UTC
Changing to default assignee for component.


Note You need to log in before you can comment on or make changes to this bug.