May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3816) Limit the target folder length to avoid path too long for Windows

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3816?page=com.atlassian.jira.plugin.... ] Jan Richter edited comment on JBDS-3816 at 5/2/16 7:28 AM: ----------------------------------------------------------- Works fine for the most part. The ability to create a too long path using mostly path delimiters is not fine though. I think the validator should first try resolving the path and then look at the length. was (Author: jrichter1): Works fine for the most part. The ability to create a too long path using mostly path delimiters is not though. I think the validator should first try resolving the path and then look at the length. > Limit the target folder length to avoid path too long for Windows > ----------------------------------------------------------------- > > Key: JBDS-3816 > URL: https://issues.jboss.org/browse/JBDS-3816 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > > Looks like no length limit is set for the target folder, this way one can run into the path too long error when installing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22237) Properties: table is not updated when resource is selected and edited

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22237?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22237. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Properties: table is not updated when resource is selected and edited > --------------------------------------------------------------------- > > Key: JBIDE-22237 > URL: https://issues.jboss.org/browse/JBIDE-22237 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > Attachments: error-upon-scale-down.png > > > When an entry is selected in a properties tab for an openshift resource and the resources changes, you can no longer edit/update that resource until its refreshed. For example while implementing scaling, I can select a dc, scale it up, but then receive an error when I immediately try to scale it down because the resource version is out of sync. > steps to reproduce: > # ASSERT: make sure that you have at least 1 application in OpenShift > # EXEC: in Explorer: select your service > # EXEC: open up Properties and select "Deployments" tab > # EXEC: pick "Scale > Up" in the context menu > # EXEC: pick "Scale > Down" in the context menu > Result: > An error is popping up telling you that the resource is outdated. > !error-upon-scale-down.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3818) Installer does not remember my selected folder until 'continue' is pressed

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3818?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3818. ----------------------------- Verified in B141. > Installer does not remember my selected folder until 'continue' is pressed > -------------------------------------------------------------------------- > > Key: JBDS-3818 > URL: https://issues.jboss.org/browse/JBDS-3818 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > For some reason installer remembers the selected folder only if it reached the confirmation page. > Log in -> select a target folder -> go back to login -> log in again -> selected folder is back to default > Log in -> select a target folder -> continue -> go back to login -> log in again -> target folder stays the way it was selected -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21927) Collect usage on LiveReload

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21927?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21927. ------------------------------- Verified in 4.4.0.Alpha1. > Collect usage on LiveReload > --------------------------- > > Key: JBIDE-21927 > URL: https://issues.jboss.org/browse/JBIDE-21927 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Measure number of installations, LiveReload server starts and maybe even number of requests, grouped by day. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22254) Deploy Image to OpenShift wizard does not render wizard upon docker connection addition

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22254?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22254. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Deploy Image to OpenShift wizard does not render wizard upon docker connection addition > --------------------------------------------------------------------------------------- > > Key: JBIDE-22254 > URL: https://issues.jboss.org/browse/JBIDE-22254 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > In Deploy Image to OpenShift wizard the Next button is not rendered as expected. If I leave selection of a docker connection as last step (at first I fill in image details and OpenShift project), upon selection of a such connection Next button does not get enabled even it all is ok. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22255. --------------------------------- Verified with OS 3 Server Adapter as well as with EAP 6.1+ server. Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Minor > Labels: openshift_v3, server, ux > Fix For: 4.4.0.Alpha1 > > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22290) Open via livereload quick access errors when no livereload server is present

by Jan Richter (JIRA)

Jan Richter created JBIDE-22290: ----------------------------------- Summary: Open via livereload quick access errors when no livereload server is present Key: JBIDE-22290 URL: https://issues.jboss.org/browse/JBIDE-22290 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload Affects Versions: 4.4.0.Alpha1 Reporter: Jan Richter The following error is produced while the livereload server is starting: {noformat} Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui". org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4522) at org.eclipse.swt.SWT.error(SWT.java:4437) at org.eclipse.swt.SWT.error(SWT.java:4408) at org.eclipse.swt.widgets.Display.error(Display.java:1186) at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765) at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400) at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:189) at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:114) at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:112) at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$2.done(LaunchLiveReloadServerCommandHandler.java:67) at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42) at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:106) at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:144) at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694) at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22290) Open via livereload quick access errors when no livereload server is present

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22290?page=com.atlassian.jira.plugi... ] Jan Richter reassigned JBIDE-22290: ----------------------------------- Assignee: Xavier Coulon > Open via livereload quick access errors when no livereload server is present > ---------------------------------------------------------------------------- > > Key: JBIDE-22290 > URL: https://issues.jboss.org/browse/JBIDE-22290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.4.0.Alpha1 > Reporter: Jan Richter > Assignee: Xavier Coulon > > The following error is produced while the livereload server is starting: > {noformat} > Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui". > org.eclipse.swt.SWTException: Invalid thread access > at org.eclipse.swt.SWT.error(SWT.java:4522) > at org.eclipse.swt.SWT.error(SWT.java:4437) > at org.eclipse.swt.SWT.error(SWT.java:4408) > at org.eclipse.swt.widgets.Display.error(Display.java:1186) > at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765) > at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400) > at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:189) > at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:114) > at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:112) > at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$2.done(LaunchLiveReloadServerCommandHandler.java:67) > at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42) > at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:106) > at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:144) > at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694) > at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22288) VPE crashes studio with JRE fatal error on Fedora 23

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22288?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22288: ------------------------------------- [~psrna] do you happen to know who is VPE QA right now and can try to reproduce this one. I do not have Fedora 23 ready to hand right now :/ > VPE crashes studio with JRE fatal error on Fedora 23 > ---------------------------------------------------- > > Key: JBIDE-22288 > URL: https://issues.jboss.org/browse/JBIDE-22288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: hs_err_pid2276.log.zip > > > Using VPE on Fedora ends up Studio crash > Works fine on Windows 10, Ubuntu 16.04 > More details can be found here - https://developer.jboss.org/message/955490 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22263) Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22263?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22263. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22263 > URL: https://issues.jboss.org/browse/JBIDE-22263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: EnvVarsEnhancement.png > > > In Deploy Image to OpenShift wizard on the wizard page containing environment variables there is a Reset button. At the moment reset works only for one environment variable at the moment. It would be nice, if reset would set all environment variables (whole table) to default state. Currently the next wizard page containing ports mapping behave in desired way (reset set ports to default values), therefore it would be nice to have it consistent across wizard pages which are next to each other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016