[
https://issues.jboss.org/browse/JBIDE-10542?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-10542 at 12/21/11 9:06 AM:
--------------------------------------------------------------------
I checked and corrected the tests. The current EGitUtils is capable of pushing to a
specific remote. The ExpressPublishMethod simply calls the wrong util method. I commented
accordingly:
{code}
// TODO: use the following instead of the current:
// EGitUtils.push("<remote name configured in
AdapterWizardPageModel#getRemoteName>"
// , EGitUtils.getRepository(p)
// , new SubProgressMonitor(monitor, 100));
EGitUtils.push(EGitUtils.getRepository(p), new SubProgressMonitor(monitor, 100));
{code}
was (Author: adietish):
I checked and corrected the tests. The current EGitUtils is capable of pushing to a
specific remote. The code that is being used in ExpressPublishMethod is wrong. I commented
accordingly:
{code}
// TODO: use the following instead of the current:
// EGitUtils.push("<remote name configured in
AdapterWizardPageModel#getRemoteName>"
// , EGitUtils.getRepository(p)
// , new SubProgressMonitor(monitor, 100));
EGitUtils.push(EGitUtils.getRepository(p), new SubProgressMonitor(monitor, 100));
{code}
OpenShift adapter is not pushing to the configured remote, it always
pushes to "origin"
---------------------------------------------------------------------------------------
Key: JBIDE-10542
URL:
https://issues.jboss.org/browse/JBIDE-10542
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.M5
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
Attachments: configured-remote.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