April 2016 - jbosstools-issues - Jboss List Archives

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22057: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > 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 > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > 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-21857) Hot class reload doesn't work on OpenShift

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-21857: -------------------------------------- Tried to do a proof of concept calling System.gc() via the debug connection. However, the second replacement still fails. No idea why at the moment. > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3752) Installer - Setup-bundled-0.0.2-20160331-23 build does not allow the user to install any packages

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3752?page=com.atlassian.jira.plugin.... ] Len DiMaggio closed JBDS-3752. ------------------------------ Problem is not seen with: Setup-bundled-0.0.2-20160401-33.exe > Installer - Setup-bundled-0.0.2-20160331-23 build does not allow the user to install any packages > ------------------------------------------------------------------------------------------------- > > Key: JBDS-3752 > URL: https://issues.jboss.org/browse/JBDS-3752 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Environment: Windows10 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: Setup-bundled-0.0.2-20160331-23.png > > > See attached screenshot - The user is able to login, but no buttons are active on the 2nd screen. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3741) Developer Studio should install under developer-studio instead of DeveloperStudio

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3741?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3741: ------------------------------------- if we have virtualbox, the DeveloperStudio should be developerstudio without dash. WDYT? > Developer Studio should install under developer-studio instead of DeveloperStudio > --------------------------------------------------------------------------------- > > Key: JBDS-3741 > URL: https://issues.jboss.org/browse/JBDS-3741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Trivial > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: directories.png > > > Currently Developer studio is installed under the folder {{DeveloperStudio}} within the installation directory. All other programs use lower case directory names for their install directory (eg vagrant, cygwun, jdk8, etc). For consistency it should be developerstudio or developer-studio. See screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3756) Have a single progress bar for the installer

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3756?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3756: --------------------------------- Labels: havoc (was: ) > Have a single progress bar for the installer > -------------------------------------------- > > Key: JBDS-3756 > URL: https://issues.jboss.org/browse/JBDS-3756 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Pete Muir > Priority: Minor > Labels: havoc > > Most installers have a single progress bar that shows the overall progress, and then text which explains which component is being installed right now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22066) Stopping debugging of OpenShift application should get application back to normal state.

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22066: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Stopping debugging of OpenShift application should get application back to normal state. > ---------------------------------------------------------------------------------------- > > Key: JBIDE-22066 > URL: https://issues.jboss.org/browse/JBIDE-22066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22058) Allow termination of remote VM in debug configuration for OpenShift app should be checked by default

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22058?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22058: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > Allow termination of remote VM in debug configuration for OpenShift app should be checked by default > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22058 > URL: https://issues.jboss.org/browse/JBIDE-22058 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22055) Import spring-petclinic validation errors

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22055?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22055: ----------------------------------- Fix Version/s: 4.4.x > Import spring-petclinic validation errors > ------------------------------------------ > > Key: JBIDE-22055 > URL: https://issues.jboss.org/browse/JBIDE-22055 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.4.x > > > Importing of spring-petclinic is with XSD errors: > Open quote is expected for attribute "border" associated with an element type "img". index.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/speed line 65 > The content of elements must consist of well-formed character data or markup. index.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test line 44 > XML document structures must start and end within the same entity. localfile.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test line 76 > The element type "meta" must be terminated by the matching end-tag "</meta>". absolute.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 29 > The element type "meta" must be terminated by the matching end-tag "</meta>". body.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 21 > The element type "meta" must be terminated by the matching end-tag "</meta>". fixed.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 25 > The element type "meta" must be terminated by the matching end-tag "</meta>". relative.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 24 > The element type "meta" must be terminated by the matching end-tag "</meta>". scroll.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 28 > The element type "meta" must be terminated by the matching end-tag "</meta>". static.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 24 > The element type "meta" must be terminated by the matching end-tag "</meta>". table.html /jboss-spring-petclinic/src/main/webapp/vendors/jquery/test/data/offset line 22 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3738: -------------------------------------- cc: [~crobson] > Getting Started / Readme for new users after Dev Platform install is complete > ----------------------------------------------------------------------------- > > Key: JBDS-3738 > URL: https://issues.jboss.org/browse/JBDS-3738 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Labels: Havoc > Fix For: 9.1.0.GA > > > Per discussion today, we need some sort of README / Getting Started Guide for new CDK users. > This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline. > Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22058) Allow termination of remote VM in debug configuration for OpenShift app should be checked by default

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22058?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22058: ----------------------------------------------- Then, maybe this issue means user ability to stop debugging. There must be another button 'Disconnect' that will do that. Should we then try to discourage in some way user from checking "Allow termination of remove VM"? > Allow termination of remote VM in debug configuration for OpenShift app should be checked by default > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22058 > URL: https://issues.jboss.org/browse/JBIDE-22058 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application. -- 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