November 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-981) NumberFormatException if you select more features to install

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-981: --------------------------------------- Summary: NumberFormatException if you select more features to install Key: JBTIS-981 URL: https://issues.jboss.org/browse/JBTIS-981 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Environment: devstudio-is-installer-10.0.0-SNAPSHOT.jar devstudio-is-runtime-installer-10.0.0-SNAPSHOT.jar Reporter: Andrej Podhradsky {code} java.lang.NumberFormatException: For input string: "null" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Long.parseLong(Long.java:589) at java.lang.Long.parseLong(Long.java:631) at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.calculateAggregateSize(DiskSpaceCheckPanel.java:71) at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.getInstallationSize(DiskSpaceCheckPanel.java:94) at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.panelActivate(DiskSpaceCheckPanel.java:36) at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864) at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475) at com.izforge.izpack.installer.InstallerFrame.skipPanel(InstallerFrame.java:1401) at com.jboss.devstudio.core.installer.UpdatePacksPanel.panelActivate(UpdatePacksPanel.java:25) at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864) at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475) at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1443) at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionPerformed(InstallerFrame.java:1585) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252) at java.awt.Component.processMouseEvent(Component.java:6535) at javax.swing.JComponent.processMouseEvent(JComponent.java:3324) at java.awt.Component.processEvent(Component.java:6300) at java.awt.Container.processEvent(Container.java:2236) at java.awt.Component.dispatchEventImpl(Component.java:4891) at java.awt.Container.dispatchEventImpl(Container.java:2294) at java.awt.Component.dispatchEvent(Component.java:4713) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466) at java.awt.Container.dispatchEventImpl(Container.java:2280) at java.awt.Window.dispatchEventImpl(Window.java:2750) at java.awt.Component.dispatchEvent(Component.java:4713) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758) at java.awt.EventQueue.access$500(EventQueue.java:97) at java.awt.EventQueue$3.run(EventQueue.java:709) at java.awt.EventQueue$3.run(EventQueue.java:703) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) at java.awt.EventQueue$4.run(EventQueue.java:731) at java.awt.EventQueue$4.run(EventQueue.java:729) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:728) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4153) Cannot install Fuse Runtime on Windows using the installer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-4153?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-4153: ----------------------------------------- The above installer do not work if you select more features to install, see JBTIS-981 > Cannot install Fuse Runtime on Windows using the installer > ---------------------------------------------------------- > > Key: JBDS-4153 > URL: https://issues.jboss.org/browse/JBDS-4153 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Priority: Blocker > Fix For: 10.x > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > > On Windows, if using the installer with the Fuse Runtime and keeping it checked, the installation fails. > i used https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.0.... > !screenshot-1.png|thumbnail! > !screenshot-2.png|thumbnail! > !screenshot-3.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-947) Installer with runtime doesn't automatically set the appropriated server

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-947?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-947: ---------------------------------- It will always go through the server adapter so there will be a query once the IDE comes up. > Installer with runtime doesn't automatically set the appropriated server > ------------------------------------------------------------------------ > > Key: JBTIS-947 > URL: https://issues.jboss.org/browse/JBTIS-947 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Attachments: search_for_runtimes.png > > > Installer with runtime doesn't automatically set the appropriated server. Instead of that there is a dialog 'Search for runtimes' when you start the IDE for the first time. > !search_for_runtimes.png|thumbnail! > Note that this is a different behavior as it is in Devstudio installer with EAP -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-947) Installer with runtime doesn't automatically set the appropriated server

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-947?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-947: ----------------------------------------- Btw is it possible to allow installing only one runtime and the selected runtime will be automatically set a server in IDE? > Installer with runtime doesn't automatically set the appropriated server > ------------------------------------------------------------------------ > > Key: JBTIS-947 > URL: https://issues.jboss.org/browse/JBTIS-947 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Attachments: search_for_runtimes.png > > > Installer with runtime doesn't automatically set the appropriated server. Instead of that there is a dialog 'Search for runtimes' when you start the IDE for the first time. > !search_for_runtimes.png|thumbnail! > Note that this is a different behavior as it is in Devstudio installer with EAP -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4153) Cannot install Fuse Runtime on Windows using the installer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-4153?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-4153: ----------------------------------------- [~dgolovin] there are 2 installers posted by Paul - devstudio-is-installer-10.0.0-SNAPSHOT.jar - devstudio-is-runtime-installer-10.0.0-SNAPSHOT.jar Please ensure that you have used the one with 'runtime' in its name. > Cannot install Fuse Runtime on Windows using the installer > ---------------------------------------------------------- > > Key: JBDS-4153 > URL: https://issues.jboss.org/browse/JBDS-4153 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Priority: Blocker > Fix For: 10.x > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > > On Windows, if using the installer with the Fuse Runtime and keeping it checked, the installation fails. > i used https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.0.... > !screenshot-1.png|thumbnail! > !screenshot-2.png|thumbnail! > !screenshot-3.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-947) Installer with runtime doesn't automatically set the appropriated server

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-947?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-947: ---------------------------------- [~apodhrad] - will close this if there are no further comments. wdyt? > Installer with runtime doesn't automatically set the appropriated server > ------------------------------------------------------------------------ > > Key: JBTIS-947 > URL: https://issues.jboss.org/browse/JBTIS-947 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > Attachments: search_for_runtimes.png > > > Installer with runtime doesn't automatically set the appropriated server. Instead of that there is a dialog 'Search for runtimes' when you start the IDE for the first time. > !search_for_runtimes.png|thumbnail! > Note that this is a different behavior as it is in Devstudio installer with EAP -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4153) Cannot install Fuse Runtime on Windows using the installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-4153?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBDS-4153: ---------------------------------- Yes - there are two - one installer without a runtime (skinny): http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... and one installer with the runtime: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... If I could get this pushed today that would be ideal (Needed for 10.2.0.GA). Thanks!!!! > Cannot install Fuse Runtime on Windows using the installer > ---------------------------------------------------------- > > Key: JBDS-4153 > URL: https://issues.jboss.org/browse/JBDS-4153 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Priority: Blocker > Fix For: 10.x > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > > On Windows, if using the installer with the Fuse Runtime and keeping it checked, the installation fails. > i used https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.0.... > !screenshot-1.png|thumbnail! > !screenshot-2.png|thumbnail! > !screenshot-3.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-23352 at 11/8/16 10:30 AM: ----------------------------------------------------------------- Well, are there any images which have ports for being listened on running container and it is not documented in Dockerfile? Mostly EXPOSE in docker file is about telling a docker where to listen. When deploying a docker image from web UI or oc binary, you dont have a choice to add ports to being listened in advance. When using a docker image to deploy on OpenShift, OpenShift automatically takes what image offers in its metadata - in this case exposes ports from metadata are used. So if user uses such image (without exposes port) for OpenShift, then oc binary and web UI cant handle it but we have a workaround for such "use cases" in tooling. Not sure whether that's correct way. Also, there was a JIRA whether a replication controller should take values from the table, if we decide to add more port mapping. If there would be no exposed ports (listening ports) it would not be possible to connect a service to such port. My 2 cents. was (Author: mlabuda): Well, are there any images which have ports for being listened on running container and it is not documented in Dockerfile? Mostly EXPOSE in docker file is about telling a docker where to listen. When deploying a docker image from web UI or oc binary, you dont have a choice to add ports to being listened in advance. So if user uses such image (without exposes port) for OpenShift, then oc binary and web UI cant handle it but we have a workaround for such "use cases" in tooling. Not sure whether that's correct way. Also, there was a JIRA whether a replication controller should take values from the table, if we decide to add more port mapping. If there would be no exposed ports (listening ports) it would not be possible to connect a service to such port. My 2 cents. > Deploy Docker Wizard: Default routing port selection need more info for users > ----------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.Final > > Attachments: no_route_selected.png, refdoc-services-1.png, refdoc-services-2.png, webui-deploy-docker-image.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. > If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. > steps to reproduce: > # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu > # EXEC: get to the "Services & Routing Settings" page > !no_route_selected.png! > It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23352: --------------------------------------- Well, are there any images which have ports for being listened on running container and it is not documented in Dockerfile? Mostly EXPOSE in docker file is about telling a docker where to listen. When deploying a docker image from web UI or oc binary, you dont have a choice to add ports to being listened in advance. So if user uses such image (without exposes port) for OpenShift, then oc binary and web UI cant handle it but we have a workaround for such "use cases" in tooling. Not sure whether that's correct way. Also, there was a JIRA whether a replication controller should take values from the table, if we decide to add more port mapping. If there would be no exposed ports (listening ports) it would not be possible to connect a service to such port. My 2 cents. > Deploy Docker Wizard: Default routing port selection need more info for users > ----------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.Final > > Attachments: no_route_selected.png, refdoc-services-1.png, refdoc-services-2.png, webui-deploy-docker-image.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. > If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. > steps to reproduce: > # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu > # EXEC: get to the "Services & Routing Settings" page > !no_route_selected.png! > It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4153) Cannot install Fuse Runtime on Windows using the installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4153?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4153: ------------------------------------- [~pleacu], it works but there is no fuse runtime in it, is that what you wanted? > Cannot install Fuse Runtime on Windows using the installer > ---------------------------------------------------------- > > Key: JBDS-4153 > URL: https://issues.jboss.org/browse/JBDS-4153 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Priority: Blocker > Fix For: 10.x > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > > On Windows, if using the installer with the Fuse Runtime and keeping it checked, the installation fails. > i used https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.0.... > !screenshot-1.png|thumbnail! > !screenshot-2.png|thumbnail! > !screenshot-3.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2016