[jbosstools-issues] [JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121613#comment-13121613 ] 

Fred Bricon edited comment on JBDS-3489 at 10/23/15 11:39 AM:
--------------------------------------------------------------

Mockup of modified UI to add workspace project selection: 
!project-selection.png!

Selecting a workspace project would trigger a number of things:
- check if the project is shared with git. If not, display error message, enable the share with git link that'd open the egit wizard
- the type of project would be determined, which, if 'Matching template's is enabled, would filter the templates of the selected openshift project per matching tags
- default selected templates could be determined by a list of hard coded template names (eg. eap6-basic-s2i, else eap6-basic-sti for EAP)
- remote git repo url and git context dir would be determined. Matching values would be injected to known template parameters (git_uri/source_repository_url, git_context_dir/context_dir), if they're present in the selected template

At the end of the application creation process, the git import wizard would NOT be called, because the project already exists in the workspace.


was (Author: fbricon):
Mockup of modified UI to add workspace project selection: 
!project-selection.png!

Selecting a workspace project would trigger a number of things:
- check if the project is shared with git. If not, display error message, enable the share with git link that'd open the egit wizard
- the type of project would be determined, which, if 'Matching template's is enabled, would filter the templates of the selected openshift project per matching tags
- default selected templates could be determined by a list of hard coded template names (eg. eap6-basic-s2i, else eap6-basic-sti for EAP)
- remote git repo url and git context dir would be determined. Matching values would be injected to known template parameters (git_uri/source_repository_url, git_context_dir/context_dir), if they're present in the selected template, 

> Publishing existing eclipse project to OpenShift
> ------------------------------------------------
>
>                 Key: JBDS-3489
>                 URL: https://issues.jboss.org/browse/JBDS-3489
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: openshift, requirements
>            Reporter: Max Rydahl Andersen
>            Assignee: Fred Bricon
>            Priority: Critical
>              Labels: openshift_v3
>             Fix For: 9.0.1.Beta1
>
>         Attachments: project-selection.bmml, project-selection.png
>
>
> As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection.
> * This is equivalent to 'oc new-app'



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)