[jbosstools-issues] [JBoss JIRA] (JBIDE-21340) Deploy from existing project git constraints are too stringent
[
https://issues.jboss.org/browse/JBIDE-21340?page=com.atlassian.jira.plugi...
]
Fred Bricon edited comment on JBIDE-21340 at 1/20/16 3:35 PM:
--------------------------------------------------------------
Fixed in master / 4.3.x. Now only a warning shows up if no HTTP(S)-based git remote is
defined.
Git-dirty projects are now allowed.
Enforcing the Git source property will be implemented later, via JBIDE-21490
was (Author: fbricon):
Fixed in master / 4.3.x. Now only a warning shows up if no HTTP(S)-based git remote is
defined.
Git-dirty projects are now allowed
Deploy from existing project git constraints are too stringent
--------------------------------------------------------------
Key: JBIDE-21340
URL: https://issues.jboss.org/browse/JBIDE-21340
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Fred Bricon
Assignee: Andre Dietisheim
Fix For: 4.3.1.Beta2
There are currently 2 constraints when deploying ane existing project to OpenShift 3 that
are really really annoying:
- if the project is shared with git but dirty, you can't proceed with project
deployment on openshift. This constraint is completely unnecessary and should be lifted
- if the project was cloned using git/ssh protocol, it can't be deployed directly
(http(s) is required). This should actually just be a warning, the user can modify the git
url to use http(s) in the next page
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)