[
https://issues.jboss.org/browse/JBIDE-19787?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-19787:
------------------------------------------
This was partially implemented. This was only implemented as explicit operation. This was
not implemented as part of the new-application wizard, we went out of time for this to
happen.
You can now select a connection or a project and pick "Import Application" from
the context menu. You'd get to the same wizard via menu
File->Import->OpenShift->Existing OpenShift Application if you select a v3
connection in the connection dialog.
!import-application.png!
You get all projects and their build configs listed:
!import-application-2.png!
As soon as you pick a build-config you can get to page2 where you specify the clone
destination:
!import-application-3.png!
As a user I want to import existing OpenShift projects into my
Eclipse workspace
--------------------------------------------------------------------------------
Key: JBIDE-19787
URL:
https://issues.jboss.org/browse/JBIDE-19787
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: import_wizard
Fix For: 4.3.0.Beta1
Attachments: import-application-2.png, import-application-3.png,
import-application.png
This is the case where a user has added resources via the CLI or console and wants to
create an Eclipse project in order to start developing.
The Eclipse project nature will be of the appropriate type as inferred from the source.
Main focus is to correctly import java/maven projects or “General” project otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)