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

[Andre Dietisheim (Issue Comment Edited) (JIRA)]

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

Andre Dietisheim edited comment on JBIDE-10171 at 12/5/11 6:20 PM:
-------------------------------------------------------------------

attached patch for the new approach. the ui is still not implemented. I took the shortest path to the new approach so that we asap get an idea if that would work. 

It pretty much looks like as if it works. I could push a dynamic web project (with seam facet) and the seambooking example. 
Currently you cannot just clone a git shared project and disconnect it. Disconnect in egit does not remove the .git folder, it just deregisters the team provider. The recursive copy I currently do will not overwrite the .git folder and seambooking then got reconnected to its local clone. To nevertheless be able to check seambooking, I simply removed the .git folder manually. I therefore guess that we should overwrite an existing .git folder when copying.
                
      was (Author: adietish):
    attached patch for the new approach. the ui is still not implemented. I took the shortest path to the new approach so that we asap get an idea if that would work. 
                  
> 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: import-exiting-project.patch, 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