[JBoss JIRA] (JBIDE-21995) Hostname is set to localhost when prompt for route is checked
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21995?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21995:
-----------------------------------------------
This method is called by only
{code}
updateServer(String serverName, String host, String connectionUrl, String deployProjectName, String serviceId, String sourcePath, String podPath, String routeURL, IServerWorkingCopy server)
{code}
and there host is set by
{code}
server.setHost(host);
{code}
so due to the interface method we do not have to use directly PROP_HOSTNAME.
We can add before setting the host
{code}
if(host == null) {
host = ""; //or "Prompt for route when multiple routes available to show in browser"
}
{code}
> Hostname is set to localhost when prompt for route is checked
> -------------------------------------------------------------
>
> Key: JBIDE-21995
> URL: https://issues.jboss.org/browse/JBIDE-21995
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> Hostname in Server Editor for an OpenShift 3 application is set to localhost if checkbox "Prompt for route when multiple routes available to show in browser" is checked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-611) Fuse quickstart is not available in JBoss Central
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-611?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-611:
------------------------------------
Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1 (was: JBDS 9.1.0.Beta2 + JBDS 9.0.0.Beta1)
> Fuse quickstart is not available in JBoss Central
> -------------------------------------------------
>
> Key: JBTIS-611
> URL: https://issues.jboss.org/browse/JBTIS-611
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE
> Affects Versions: 9.0.0.Beta1
> Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Attachments: fuse1.png
>
>
> The fuse quickstart is not available in JBoss Central in JBDS 9.1.0.Beta2 (without Fuse tooling). This is ok because Fuse tooling is on earlyaccess.
> The problem is that the quickstart is not available even it we install the Fuse tooling.
> Note that the quickstart is available in JBDS 9.0.0.GA + JBDS-IS 9.0.0.Alpha2 earlyaccess.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3635:
-----------------------------------
Adding angular-messages to jspm dependencies in package.json should do the trick and fix it
> Add the ability to detect/select existing dependencies/tools
> ------------------------------------------------------------
>
> Key: JBDS-3635
> URL: https://issues.jboss.org/browse/JBDS-3635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: pdkinstaller.png, Technologies 5.pdf
>
>
> It would be great if the installer allowed the user to use some of the required tools they have already installed.
> The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc.
> The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter):
> !pdkinstaller.png|thumbnail!
> [~dgolovin] & [~crobson], what's your opinion on this?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21998) "Open in Web browser" displays a dialog to select a route
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21998?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21998:
------------------------------------------
[~xcoulon] I agree that we shouldnt show up the router chooser if there's only 1 possible route for the selected service. We should fix this, but we should still show the dialog if there's more than 1 possibel route.
> "Open in Web browser" displays a dialog to select a route
> ---------------------------------------------------------
>
> Key: JBIDE-21998
> URL: https://issues.jboss.org/browse/JBIDE-21998
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.CR1
>
> Attachments: Screenshot 2016-03-30 00.20.48.png
>
>
> I have an OpenShift project with 2 services: one {{eap-app}} and one NodeJS.
> For the {{eap-app}} service, I have a corresponding server adapter.
> When I select {{<eap-app server adapter> > Show In > Web Browser}}, I have the following dialog to select a route, but that seems wrong because I already selected the {{eap-app}} service, so there's no reason to propose me the route to the NodeJS service.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK (2.0.0.Beta5)
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-22004:
-------------------------------
Summary: Runtime detection unable to detect CDK (2.0.0.Beta5) (was: Runtime detection can't recognize CDK (2.0.0.Beta5))
> Runtime detection unable to detect CDK (2.0.0.Beta5)
> ----------------------------------------------------
>
> Key: JBIDE-22004
> URL: https://issues.jboss.org/browse/JBIDE-22004
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.1.CR1
> Reporter: Radim Hopp
>
> Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it.
> Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3635:
-----------------------------------
[~dgolovin] You just broke both the tests and the installer itself with https://github.com/redhat-developer-tooling/developer-platform-install/pu...
It does not work in any form or shape I tried - it just presents a blank window.
This is what I'm getting from the console:
{noformat}file:///home/jrichter/Git/developer-platform-install/browser/angular-messages.js Failed to load resource: net::ERR_FILE_NOT_FOUND
Uncaught (in promise) Error: Error: XHR error loading file:///home/jrichter/Git/developer-platform-install/browser/angular-messages.js
Error loading file:///home/jrichter/Git/developer-platform-install/browser/angular-messages.js as "angular-messages" from file:///home/jrichter/Git/developer-platform-install/browser/main.js{noformat}
Looks like an unresolved import for angular-messages.js file.
> Add the ability to detect/select existing dependencies/tools
> ------------------------------------------------------------
>
> Key: JBDS-3635
> URL: https://issues.jboss.org/browse/JBDS-3635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: pdkinstaller.png, Technologies 5.pdf
>
>
> It would be great if the installer allowed the user to use some of the required tools they have already installed.
> The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc.
> The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter):
> !pdkinstaller.png|thumbnail!
> [~dgolovin] & [~crobson], what's your opinion on this?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22004) Runtime detection can't recognize CDK (2.0.0.Beta5)
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-22004:
----------------------------------
Summary: Runtime detection can't recognize CDK (2.0.0.Beta5)
Key: JBIDE-22004
URL: https://issues.jboss.org/browse/JBIDE-22004
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.3.1.CR1
Reporter: Radim Hopp
Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it.
Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21992:
-------------------------------------
LGTM
> Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21992
> URL: https://issues.jboss.org/browse/JBIDE-21992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Labels: deploy_docker_wizard
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: deploy-config-scalability-page.png, deployment-config-page.png, DeploymentConfigLayout.png
>
>
> The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way.
> !deploy-config-scalability-page.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years