[JBoss JIRA] (JBDS-4113) uninstaller folder is empty after installation is done
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4113?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4113.
-----------------------------
Verified in B172.
> uninstaller folder is empty after installation is done
> ------------------------------------------------------
>
> Key: JBDS-4113
> URL: https://issues.jboss.org/browse/JBDS-4113
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
>
> After installation uninstaller folder is empty and there is error message in install.log file
> {code}
> Thu, 13 Oct 2016 23:52:18 GMT-ERROR: Data - Error: ENOENT: no such file or directory, lstat 'C:\p\rh\dpi\transpiled\browser\uninstaller\uninstall.ps1'
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23134) Improve UI of Deployment tab of Runtime Editor
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23134?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23134.
---------------------------------
There is one minor glitch in the result - the filter text field is now 2 lines tall on my mac. I created a followup issue here: JBIDE-23361
Closing this.
Verified in devstudio-10.2.0.AM2-v20161011-0458-B6186-installer-standalone.jar
> Improve UI of Deployment tab of Runtime Editor
> ----------------------------------------------
>
> Key: JBIDE-23134
> URL: https://issues.jboss.org/browse/JBIDE-23134
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM2
>
> Attachments: screenshot-1.png
>
>
> - Refresh table button is really strange
> - there are some grey background around the sections
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23361) Filter text field in Server Editor's Deployment tab is too tall
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23361?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23361:
----------------------------------
Description:
After JBIDE-23134 changed the overall layout of the Deployment tab in Server Editor and the modules table, the filter text field is now too tall, as if it was 2 lines high.
Otherwise it seems to work perfectly fine.
!deployment-filter.png!
was:
After JBIDE-23134 changed the overall layout of the Deployment tab in Server Editor and the modules table, the filter text field is now too tall, as if it was 2 lines high.
Otherwise it seems to work perfectly fine.
> Filter text field in Server Editor's Deployment tab is too tall
> ---------------------------------------------------------------
>
> Key: JBIDE-23361
> URL: https://issues.jboss.org/browse/JBIDE-23361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Attachments: deployment-filter.png
>
>
> After JBIDE-23134 changed the overall layout of the Deployment tab in Server Editor and the modules table, the filter text field is now too tall, as if it was 2 lines high.
> Otherwise it seems to work perfectly fine.
> !deployment-filter.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23361) Filter text field in Server Editor's Deployment tab is too tall
by Martin Malina (JIRA)
Martin Malina created JBIDE-23361:
-------------------------------------
Summary: Filter text field in Server Editor's Deployment tab is too tall
Key: JBIDE-23361
URL: https://issues.jboss.org/browse/JBIDE-23361
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.2.AM2
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Minor
After JBIDE-23134 changed the overall layout of the Deployment tab in Server Editor and the modules table, the filter text field is now too tall, as if it was 2 lines high.
Otherwise it seems to work perfectly fine.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: No port is selected by default to be used for routing
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23352:
----------------------------------
Issue Type: Enhancement (was: Bug)
> Deploy Docker Wizard: No port is selected by default to be used for routing
> ---------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Attachments: no_route_selected.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port.
> If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it.
> !no_route_selected.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: No port is selected by default to be used for routing
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23352:
----------------------------------
Description:
In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port (but by default OpenShift know what to open.
If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it.
!no_route_selected.png!
was:
In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port.
If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it.
!no_route_selected.png!
> Deploy Docker Wizard: No port is selected by default to be used for routing
> ---------------------------------------------------------------------------
>
> Key: JBIDE-23352
> URL: https://issues.jboss.org/browse/JBIDE-23352
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
> Attachments: no_route_selected.png
>
>
> In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default and thus finishing the wizard as it is result into an routing with no mapped port (but by default OpenShift know what to open.
> If there is only one port mapping, we should check it by default. If there are more port mappings, we should use some heuristics to check it.
> !no_route_selected.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months