March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21857: ------------------------------------- Sprint: devex #123 November 2016, devex #129 March 2017 (was: devex #123 November 2016, devex #128 February 2017) > Hot code replacement 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: Andre Dietisheim > Fix For: 4.4.4.AM2 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > 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 (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23422: ------------------------------------- Sprint: devex #129 March 2017 (was: devex #128 February 2017) > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Andre Dietisheim > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.4.AM2 > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3866: ------------------------------------- I will take a look. > vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server > ---------------------------------------------------------------------------------------- > > Key: JBDS-3866 > URL: https://issues.jboss.org/browse/JBDS-3866 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (previous installs of CDK and dependencies) > Reporter: Robert Terzi > Assignee: Rob Stryker > Fix For: 10.4.0.AM2 > > > vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse. > The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist. > The CDK server was shown as 'Started, Sychronized'. > The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either. > Synchronized seems misleading here, since no files had been sync'd yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24091) Forge New and Noteworthy for 4.4.4.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24091?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24091: ------------------------------------ For the record, that should be done at the end of the sprint. I am now creating the JIRAs as the sprint start so we can have them on our JIRA sprint board > Forge New and Noteworthy for 4.4.4.AM2 > --------------------------------------------------- > > Key: JBIDE-24091 > URL: https://issues.jboss.org/browse/JBIDE-24091 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.4.AM2 > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24086 #comment Create N&N for Forge 4.4.4.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23658) Hibernate console configuration wizard problems - and no way to get specifics

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23658?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23658: ------------------------------ Fix Version/s: 4.4.4.AM2 4.5.0.AM1 (was: 4.4.4.AM1) > Hibernate console configuration wizard problems - and no way to get specifics > ----------------------------------------------------------------------------- > > Key: JBIDE-23658 > URL: https://issues.jboss.org/browse/JBIDE-23658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.4.2.Final > Environment: Neon.1 and Neon.2, Windows 7, targeting Oracle > Reporter: Jesper Skov > Assignee: Koen Aers > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: empty-clean.zip > > > Creating a Hibernate Console Configuration using the wizard fails for most of our projects. > All the feedback we have is the text in red: "Could not create JPA based Configuration" > I would have liked to qualify this problem report with some more information. But there is no problems reported in the eclipse log. > I have tried enabling debugging, as per http://docs.jboss.org/tools/latest/en/hibernatetools/html/plugins.html#de..., without getting any output to the Eclipse Error console, or to the hibernate log file. > We wonder if maybe the plugin/perspective is just dead (or dying). > The plugin documentation has snapshots from 2010/2011, and the JBossTools documentation itself (http://docs.jboss.org/tools/latest/) was not updated since 4.1.0/2013. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24091) Forge New and Noteworthy for 4.4.4.AM2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24091?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-24091. ----------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.4.4.AM2 > --------------------------------------------------- > > Key: JBIDE-24091 > URL: https://issues.jboss.org/browse/JBIDE-24091 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.4.4.AM2 > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24086 #comment Create N&N for Forge 4.4.4.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24021) Properties file are not reloaded

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24021?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24021: ------------------------------- Story Points: 8 > Properties file are not reloaded > -------------------------------- > > Key: JBIDE-24021 > URL: https://issues.jboss.org/browse/JBIDE-24021 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Affects Versions: 4.4.3.Final > Reporter: Robert Paasche > Assignee: Jeff MAURY > Fix For: 4.4.4.AM2 > > > After updating an open properties file with "git pull" the file isn't reloaded by the editor. > This makes the editor useless in multi-developer environments. > BTW. the egit plugin shows there are something changed (new line for example) on the left border. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19391) Properties File editor does not work properly

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19391?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19391: ------------------------------- Story Points: 2 (was: 5) > Properties File editor does not work properly > --------------------------------------------- > > Key: JBIDE-19391 > URL: https://issues.jboss.org/browse/JBIDE-19391 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Reporter: Ali Hopyar > Assignee: Jeff MAURY > Fix For: 4.4.4.AM2 > > Attachments: messages_en.properties > > > On eclipse luna, I can not use JBoss editor for properties files. When I clicked add button nothing happens. When I click source tab and try to add some property, it is disappears when saved. Also if I open a property file that has been written before, also its content disappears. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23055) Repeated toggling of JAX-RS support on project does not cause it to rebuild

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23055?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23055: ------------------------------- Story Points: 8 > Repeated toggling of JAX-RS support on project does not cause it to rebuild > --------------------------------------------------------------------------- > > Key: JBIDE-23055 > URL: https://issues.jboss.org/browse/JBIDE-23055 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.4.1.AM3 > Reporter: Jan Richter > Assignee: Jeff MAURY > Fix For: 4.4.4.AM2 > > > When JAX-RS support is toggled in a project's preferences, clicking Apply will rebuild the project and JAX-RS services will (dis)/appear and validation is enabled/disabled. > But if without closing the preferences I toggle JAX-RS support again and press Apply, nothing happens - the project is not built with the new settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19391) Properties File editor does not work properly

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19391?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-19391: ------------------------------- Story Points: 5 > Properties File editor does not work properly > --------------------------------------------- > > Key: JBIDE-19391 > URL: https://issues.jboss.org/browse/JBIDE-19391 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Reporter: Ali Hopyar > Assignee: Jeff MAURY > Fix For: 4.4.4.AM2 > > Attachments: messages_en.properties > > > On eclipse luna, I can not use JBoss editor for properties files. When I clicked add button nothing happens. When I click source tab and try to add some property, it is disappears when saved. Also if I open a property file that has been written before, also its content disappears. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017