[JBoss JIRA] (JBDS-3862) Platform installer failed to detect existing Cygwin install with ssh and sftp
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3862?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3862:
--------------------------------
Attachment: screenshot-1.png
> Platform installer failed to detect existing Cygwin install with ssh and sftp
> -----------------------------------------------------------------------------
>
> Key: JBDS-3862
> URL: https://issues.jboss.org/browse/JBDS-3862
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit,
> Cygwin 2.5.1 already installed in the detault location C:\cygwin.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.1.0.AM3
>
> Attachments: screenshot-1.png
>
>
> The installer did not detect the existing Cygwin install in C:\Cygwin.
> What test is used to determine if Cygwin is already installed?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22916:
-------------------------------
Sprint: devex #119 August 2016
> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22916
> URL: https://issues.jboss.org/browse/JBIDE-22916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.1.Final
>
>
> When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest".
> You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22916:
-------------------------------
Fix Version/s: 4.4.1.Final
> Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-22916
> URL: https://issues.jboss.org/browse/JBIDE-22916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.1.Final
>
>
> When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest".
> You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-6100) Unambiguous hibernate configuration values in hibernate console
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6100?page=com.atlassian.jira.plugin... ]
Koen Aers updated JBIDE-6100:
-----------------------------
Sprint: (was: devex #119 August 2016)
> Unambiguous hibernate configuration values in hibernate console
> ---------------------------------------------------------------
>
> Key: JBIDE-6100
> URL: https://issues.jboss.org/browse/JBIDE-6100
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 3.1.0.GA
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
>
> There are some situations where hibernate console setting can be uncertain. It should be improved, for example:
> Hibernate dialect is defined in hibernate.cfg.xml file and in options tab. Which value has priority? Such values should be active only on one place and should be unambiguous. Same for other duplicate values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months