[
https://issues.jboss.org/browse/JBIDE-21152?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-21152:
-------------------------------------
Ok so actually the error message is a bit misleading. The actual problem is "No
remote HTTPS Git repository is defined..."
OpenShift needs to be able to clone the target repository. So it must be public or at
least available to that OpenShift instance, and can not require authentication to clone.
For that reason we only support HTTPS repos. See
https://help.github.com/articles/which-remote-url-should-i-use/ for more details.
I can use the jboss-eap-quickstarts just fine.
But maybe we should display a warning instead, and let the user manually type a HTTPS
based url in parameters page
Cannot deploy mvn module of an existing git-based application to
OpenShift 3 server
-----------------------------------------------------------------------------------
Key: JBIDE-21152
URL:
https://issues.jboss.org/browse/JBIDE-21152
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Marián Labuda
Assignee: Fred Bricon
Priority: Critical
Attachments: application_wizard.png
If a git-based project it maven module and it has some parent (like eap quickstarts
available at
https://github.com/jboss-developer/jboss-eap-quickstarts) it is not possible
to deploy such a project. There is an error in New OpenShift Application wizard telling
that a project is not git project, although it is. There was similar issue with OpenShift
2 and with deploying projects which did not have .git folder in itself but it was in
parent. See following screenshot:
!application_wizard.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)