[jbosstools-issues] [JBoss JIRA] (JBIDE-10171) OpenShift Express Use Case Scenario
Andre Dietisheim (Commented) (JIRA)
jira-events at lists.jboss.org
Tue Dec 6 18:24:41 EST 2011
[ https://issues.jboss.org/browse/JBIDE-10171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648650#comment-12648650 ]
Andre Dietisheim commented on JBIDE-10171:
------------------------------------------
I now implemented the following approach:
* checkbox "create new project" that is checked by default, which will allow you to import the OpenShift Application to your workspace
* added a text field and a browse button that are enabled if you uncheck "create new project"
* the browse button will allow you to choose among projects in your workspace. Valid projects are
* not (team) shared
* has no .git folder
* is an Eclipse WTP project
* if the checkbox "create new project" is unchecked, you'll get the chosen project "OpenShift enabled". I add the OpenShift configuration files (.openshift, deployments, .git, pom.xml - No file is overwritten if it already exists), connect it to a git repo and commit the files within the project.
* If you choose to "OpenShift enable" your existing project, you'll get warning about the imminent modifications.
The missing corrections are the following:
* I should create (if it does not exist yet) a .gitignore file which will cover the following items
* target
* .settings
* .project
* .classpath
* .factorypath
@Max: please review what's currently in trunk. The only item that is not there yet, is the .gitignore file
> 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
> 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
More information about the jbosstools-issues
mailing list