[
https://issues.jboss.org/browse/FORGEPLUGINS-89?page=com.atlassian.jira.p...
]
Rafael Benevides edited comment on FORGEPLUGINS-89 at 10/5/12 2:03 PM:
-----------------------------------------------------------------------
rhc setup will warn in case of existing previous application on Openshift (and use it if
you agree).
During setup, you can add the diferent openshift remote repo name.
Commit:
https://github.com/rafabene/plugin-openshift/commit/e2f72c5d05609eff16053...
was (Author: rafabene):
rhc setup will warn in case of existing previous application on Openshift.
During setup, you can add the diferent openshift remote repo name.
Commit:
https://github.com/rafabene/plugin-openshift/commit/e2f72c5d05609eff16053...
Openshift plugin should handle the setup when previous openshift app
exists
---------------------------------------------------------------------------
Key: FORGEPLUGINS-89
URL:
https://issues.jboss.org/browse/FORGEPLUGINS-89
Project: Forge Plugins
Issue Type: Enhancement
Reporter: Rafael Benevides
Assignee: Rafael Benevides
Labels: forge, openshift, plugin
One item I got is that we check if the projects setup by JBoss Tools, openshift client
and OpenShift Forge client are compatible or can be made compatible.
i.e. forge *always* uses "openshift" as the remote afaik - openshift client
always create projects where the remote is in "origin" - as a consequence jboss
tools
added support for naming the remote used so you could align them.
If openshift could allow naming the remote or pick up the existing remote pointing to
openshift these things could be aligned.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira