[jbosstools-issues] [JBoss JIRA] (JBIDE-21340) Deploy from existing project git constraints are too stringent
Nick Boldt (JIRA)
issues at jboss.org
Wed Dec 16 12:08:00 EST 2015
[ https://issues.jboss.org/browse/JBIDE-21340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142041#comment-13142041 ]
Nick Boldt commented on JBIDE-21340:
------------------------------------
Slip to Beta2; not a blocker for Beta1.
> 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)
More information about the jbosstools-issues
mailing list