[jbosstools-issues] [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario

[Max Rydahl Andersen (Commented) (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------

Okey so here is the thing we came up with (its similar to what have been discussed previously but "scoped" for M5 and then we can look at making things more easily available after M5):

- In the OpenShift Wizard on its last page, we will add a way to optionally select *one* existing project (<userproject>).
- If no userproject is specified the wizard behaves as it does now: git clone into a directory, import that directory as a project.
- IF userproject is specified the wizard will do something similar to:
    * cd <userproject> 
    * git init
    * git add remote <remote-name> <openshift-app-url>
    * git merge ... -X ours
    
This should bring that project in eclipse to look just the same as if it was an git cloned project.
And it will work for all types of openshift apps.

For M5 the userproject:
- cannot have any existing Team providers (svn, egit, mecurial etc.) enabled on the project.
- if there are any .git folders already in its root we probably won't handle that so should check for that too and filter/warn if user chooses such a project.
- will not have pom.xml altered/checked for existence of 'openshift' profile for AS7 style apps.


after M5 we should look at handling the addition of openshift profile to pom.xml etc.
plus also make this setup possibly to do directly from the context menu of the project.

WDYT?
                
> OpenShift Express Use Case Scenario
> -----------------------------------
>
>                 Key: JBIDE-10171
>                 URL: https://issues.jboss.org/browse/JBIDE-10171
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>            Reporter: Burr Sutter
>            Assignee: Max Rydahl Andersen
>            Priority: Critical
>             Fix For: 3.3.0.M5
>
>         Attachments: merge-with-unknown.png, not-compatible.png, selectable-examples.png
>
>
> Here is the workflow:
> 1) User starts with one of the 4 key archetypes (ee6  war, ee6 ear, springmvc, html5) to create a default application
> 2) deploys that app to a local JBoss instance to manually test
> 3) user sets up a New Server attached to an application at OpenShift Express
> 4) User now deploys the project created in step 1 above to the openshift express server
> And a related workflow:
> 1) User imports a pre-existing Maven project
> 2) Adjusts his dependencies for JBoss AS deployment
> 3) deploys and tests on a localhost version of JBoss AS7
> 4) Configures a OpenShift Server in the Servers tab
> 5) Deploys to Openshift

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira