[jbosstools-issues] [JBoss JIRA] (JBIDE-21526) Deploy from existing project git constraints are too stringent
Radim Hopp (JIRA)
issues at jboss.org
Wed May 4 08:45:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radim Hopp closed JBIDE-21526.
------------------------------
Verified in JBDS 10.0.0.Alpha1. Closing.
> Deploy from existing project git constraints are too stringent
> --------------------------------------------------------------
>
> Key: JBIDE-21526
> URL: https://issues.jboss.org/browse/JBIDE-21526
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Fix For: 4.4.0.Alpha1
>
>
> 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