April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22057: ----------------------------------------------- Then, if some changes are made when running in debug mode, one more rsync is probably needed when restarting after in the non-debug mode. > Changes done to OpenShift application are thrown away when debugging is enabled > ------------------------------------------------------------------------------- > > Key: JBIDE-22057 > URL: https://issues.jboss.org/browse/JBIDE-22057 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3, respin-b, server_adapter > Fix For: 4.3.1.CR1 > > > When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different. > I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21841 at 4/5/16 5:57 PM: ------------------------------------------------------------------ [~fbricon] [~jeffmaury] we have a detail pane mechanism that spares you from coding the boiler plate mostly. You can see an exemplary usage in the [TemplateListPage|https://github.com/jbosstools/jbosstools-openshift/blob/...] or [ServerSettingsWizardPage|https://github.com/jbosstools/jbosstools-openshi...]. The selected build config is available in ImportApplicationWizardModel#getSelectedItem. was (Author: adietish): [~fbricon] [~jeffmaury] we have a detail pane mechanism that spares you from coding the boiler plate mostly. You can see an exemplary usage in the [ServerSettingsWizardPage|https://github.com/jbosstools/jbosstools-openshi...]. The selected build config is available in ImportApplicationWizardModel#getSelectedItem. > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21841 at 4/5/16 5:53 PM: ------------------------------------------------------------------ [~fbricon] [~jeffmaury] we have a detail pane mechanism that spares you from coding the boiler plate mostly. You can see an exemplary usage in the [ServerSettingsWizardPage#https://github.com/jbosstools/jbosstools-openshi...]. The selected build config is available in ImportApplicationWizardModel#getSelectedItem. was (Author: adietish): [~fbricon][~jeffmaury] we have a detail pane mechanism that spares you from coding the boiler plate mostly. You can see an exemplary usage in the [ServerSettingsWizardPage#https://github.com/jbosstools/jbosstools-openshi...]. The selected build config is available in ImportApplicationWizardModel#getSelectedItem. > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21841 at 4/5/16 5:53 PM: ------------------------------------------------------------------ [~fbricon] [~jeffmaury] we have a detail pane mechanism that spares you from coding the boiler plate mostly. You can see an exemplary usage in the [ServerSettingsWizardPage|https://github.com/jbosstools/jbosstools-openshi...]. The selected build config is available in ImportApplicationWizardModel#getSelectedItem. was (Author: adietish): [~fbricon] [~jeffmaury] we have a detail pane mechanism that spares you from coding the boiler plate mostly. You can see an exemplary usage in the [ServerSettingsWizardPage#https://github.com/jbosstools/jbosstools-openshi...]. The selected build config is available in ImportApplicationWizardModel#getSelectedItem. > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21841: ------------------------------------------ [~fbricon][~jeffmaury] we have a detail pane mechanism that spares you from coding the boiler plate mostly. You can see an exemplary usage in the [ServerSettingsWizardPage#https://github.com/jbosstools/jbosstools-openshi...]. The selected build config is available in ImportApplicationWizardModel#getSelectedItem. > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22115) Truncated error message display connecting to server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22115: ------------------------------------------ This is an obvious and well known issue in general. The title area is limited in its vertical size and can thus only display a limited amount of text, whether error or descriptive one. The only way we can "fix" this is to shorten the error message. > Truncated error message display connecting to server > ---------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Viacheslav Kabanovich > Priority: Minor > Attachments: bad_token_1.png, bad_token_2.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22113) CDK shutdown always goes to Forcing shutdown of VM on Windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22113?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22113: ---------------------------------------- cc: [~hardy.ferentschik] > CDK shutdown always goes to Forcing shutdown of VM on Windows > ------------------------------------------------------------- > > Key: JBIDE-22113 > URL: https://issues.jboss.org/browse/JBIDE-22113 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > > On OS X, when I stop CDK in JBDS, I get this in the console: > ==> default: Unregistering box with vagrant-registration... > ==> default: Attempting graceful shutdown of VM... > And a few seconds later, the server adapter shows "Stopped". > Today while testing on Windows I noticed that it behaves differently. > It first displays these two lines, but it keeps "Stopping". And eventually there is another line in the console which says: > ==> default: Forcing shutdown of VM... > After this, the server adapter shows "Stopped". > So for some unknown reason, on Windows the graceful shutdown fails to work. > This is JBDS+CDK installed from the latest windows installer (built April 4th). > It would be good to see if others see this on Windows as well or not. > Interestingly, when I just tried "vagrant halt" from cygwin instead of in JBDS, it stops normally - graceful shutdown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22115) Truncated error message display connecting to server

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22115: -------------------------------------- Assignee: Viacheslav Kabanovich (was: Max Rydahl Andersen) Slava, could you please take a look. > Truncated error message display connecting to server > ---------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Viacheslav Kabanovich > Priority: Minor > Attachments: bad_token_1.png, bad_token_2.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22115) Truncated error message display connecting to server

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22115: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-22115 (was: JBDS-3770) Workflow: GIT Pull Request workflow (was: CDW v1) Docs QE Status: (was: NEW) Component/s: openshift (was: openshift) Target Release: (was: 9.1.0.GA) Affects Version/s: (was: 9.1.0.CR1) > Truncated error message display connecting to server > ---------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Max Rydahl Andersen > Priority: Minor > Attachments: bad_token_1.png, bad_token_2.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22075: ----------------------------------- Summary: Confusing error message when trying to attach remote debugger to OS app run in debug mode (was: Cannot debug OpenShift application) > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016