[
https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10171:
---------------------------------------------
Andre's is now in JBIDE-10313, it was doing an attempt to at least be able to feed new
applications into the newly created openshift applications since at first run through it
was simpler than handling the full problem of existing projects. Thus it was looked into
as the best stopgap for M5.
It though turned out that the operations/code needed to do that is more or less exactly
the same to be able to provide the workflow I added above for "fresh new eclipse
projects" - so that is now what we are trying to get at since that usecase is more
important in merging from existing git projects.
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