]
Andre Dietisheim updated JBIDE-10171:
-------------------------------------
Release Notes Text: In M4 the JBoss Tools OpenShift wizard allowed you to import the
OpenShift demo app (that is created when you create a new OpenShift application) to your
workspace. M5 now offers you to push an Eclipse WTP ("Dynamic Web Project")
project from your workspace to an OpenShift application. To do that you'd have to
uncheck "Create new project" and select the project (in your workspace) that
shall be pushed to OpenShift. (was: In M4 the JBoss Tools OpenShift wizard allowed you to
check out the OpenShift demo app that is created when you create a new OpenShift
application on the platform. M5 now offers you to push an Eclipse WTP ("Dynamic Web
Project") project from your workspace to an OpenShift application.)
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
Labels: new_and_noteworthy
Fix For: 3.3.0.M5, 3.3.0.Beta1
Attachments: choose-existing-project.png, create-new-project.png,
import-existing-project2.patch, import-exiting-project.patch, merge-with-unknown.png,
not-compatible.png, selectable-examples.png, use-existing-project.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: