Bug 1267484

Summary: [DOCS] [3.1] [Feature] Document Eclipse Port Forwarding Feature
Product: OpenShift Container Platform Reporter: Vikram Goyal <vigoyal>
Component: DocumentationAssignee: Thien-Thi Nguyen <tnguyen>
Status: CLOSED UPSTREAM QA Contact: Vikram Goyal <vigoyal>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: high    
Version: 3.0.0CC: amelicha, aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-07 17:42:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Deadline: 2015-11-13   

Description Vikram Goyal 2015-09-30 07:32:51 UTC
Based on the Developer Trello Card on Eclipse Port Forwarding:

https://trello.com/c/NwFUVKFJ/59-2-as-an-eclipse-user-i-would-like-to-be-able-to-port-forward-to-my-pod

Comment 2 Thien-Thi Nguyen 2015-10-07 01:52:44 UTC
@Vikram

I don't think this really belongs as an OpenShift issue.
IDE support for port forwarding is already documented:

 http://tools.jboss.org/documentation/howto/openshift_debug.html#enableportforwarding

The current dev_guide/jboss_tools.adoc merely points at Jboss Tools generally; i don't see how another (deep) link would help.  Unless there are objections soon, i will close this BZ by end of week.

Anyway, moving state to ASSIGNED.

Comment 4 Thien-Thi Nguyen 2015-10-07 17:42:00 UTC
I've investigated further, to exclude the possibility that this is a v2 issue wrongly diagnosed as v3.  Turns out, that is not the case.  So, moving state to CLOSED:UPSTREAM, since the docs for the feature are indeed upstream.