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

[Marius Bogoevici (Commented) (JIRA)]

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

Marius Bogoevici commented on JBIDE-10171:
------------------------------------------

Discussion from a separate e-mail thread: one way to address a part of this scenario for archetypes would be to include the OpenShift profile in the archetype-generated projects (with a possible switch to disable its inclusion, upon request). 

This will make easy for developers to create projects that may deploy in OpenShift. Even if it still requires copying the generated project into the Git repo of OpenShift, it prevents users from actually tampering with the code in order to make it deployable, which is a good thing, IMO.

There are a few extra things to be said about adding the profile to archetypes: it does solve a part of the problem for newly generated projects and is IDE-independent (i.e. this can be done in Netbeans, Intellij, command line, provided that the Git commit/push are done manually). For existing projects, as well as dealing with the Git aspects of actually running in OpenShift, tooling support would still be still necessary.



                
> 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: Andre Dietisheim
>            Priority: Critical
>
> 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