[
https://issues.jboss.org/browse/JBIDE-10479?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10479 at 12/20/11 9:19 AM:
--------------------------------------------------------------------
Since there's no RECURSIVE merging strategy available for egit/jgit, we'd have to
push force to the remote imho.
I see the following approach:
* add the openshift repo as remote repo
* add deployments folder
* add .openshift folder
* add openshift profile to pom
* push force to openshift
was (Author: adietish):
Since there's no RECURSIVE merging strategy available for egit/jgit, we'd have
to push force to the remote imho.
I see the following approach:
* add the openshift repo as remote repo
* add .openshift folder
* add openshift profile to pom
* push force to openshift
UserStory: I have a project with existing .git repo, I want to use
OpenShift
----------------------------------------------------------------------------
Key: JBIDE-10479
URL:
https://issues.jboss.org/browse/JBIDE-10479
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Blocker
Fix For: 3.3.0.Beta1
Attachments: openshift_new_project_strategies.bmml,
openshift_new_project_strategies.png
--
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