[JBoss JIRA] (JBIDE-21411) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21411?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21411:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.Beta2)
> v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21411
> URL: https://issues.jboss.org/browse/JBIDE-21411
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: edit-template-parameter-value.png, required-value-decoration.png
>
>
> # ASSERT: make sure that you have a connection to a v3 OpenShift server
> # EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection
> # ASSERT: new application wizard pops up, listing your project
> # EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next"
> # EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit"
> # ASSERT: editing dialog pops up
> Result:
> !edit-template-parameter-value.png!
> "OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value?
> # EXEC: provide some value and back in the wizard page hit "Next"
> # ASSERT: "Resource Labels" page shows up.
> # EXEC: Hit "Add"
> # ASSERT: dialog pops up so that I can create a new label
> Result:
> !required-value-decoration.png!
> The dialog decorates missing values with a red error marker.
> In OpenShift tooling we usually use "*" when required values are missing, not the error icon.
> Notice also the 2 additional error-decorations that are shown (there are 4 error decorations while we should have 2 only)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21411) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21411?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21411:
------------------------------------------
merged and pushed to master
> v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21411
> URL: https://issues.jboss.org/browse/JBIDE-21411
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: edit-template-parameter-value.png, required-value-decoration.png
>
>
> # ASSERT: make sure that you have a connection to a v3 OpenShift server
> # EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection
> # ASSERT: new application wizard pops up, listing your project
> # EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next"
> # EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit"
> # ASSERT: editing dialog pops up
> Result:
> !edit-template-parameter-value.png!
> "OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value?
> # EXEC: provide some value and back in the wizard page hit "Next"
> # ASSERT: "Resource Labels" page shows up.
> # EXEC: Hit "Add"
> # ASSERT: dialog pops up so that I can create a new label
> Result:
> !required-value-decoration.png!
> The dialog decorates missing values with a red error marker.
> In OpenShift tooling we usually use "*" when required values are missing, not the error icon.
> Notice also the 2 additional error-decorations that are shown (there are 4 error decorations while we should have 2 only)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21411) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21411?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21411:
----------------------------------------
Assignee: Viacheslav Kabanovich
Resolution: Done
> v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21411
> URL: https://issues.jboss.org/browse/JBIDE-21411
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: edit-template-parameter-value.png, required-value-decoration.png
>
>
> # ASSERT: make sure that you have a connection to a v3 OpenShift server
> # EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection
> # ASSERT: new application wizard pops up, listing your project
> # EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next"
> # EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit"
> # ASSERT: editing dialog pops up
> Result:
> !edit-template-parameter-value.png!
> "OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value?
> # EXEC: provide some value and back in the wizard page hit "Next"
> # ASSERT: "Resource Labels" page shows up.
> # EXEC: Hit "Add"
> # ASSERT: dialog pops up so that I can create a new label
> Result:
> !required-value-decoration.png!
> The dialog decorates missing values with a red error marker.
> In OpenShift tooling we usually use "*" when required values are missing, not the error icon.
> Notice also the 2 additional error-decorations that are shown (there are 4 error decorations while we should have 2 only)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21410) Improve source path validation in New OpenShift 3 server adapter wizard
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21410:
-------------------------------------
Summary: Improve source path validation in New OpenShift 3 server adapter wizard
Key: JBIDE-21410
URL: https://issues.jboss.org/browse/JBIDE-21410
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Marián Labuda
First point: In New OpenShift 3 server adapter wizard there is a text label for Source path. Currently there is only not null validation, if there is no path, next button is disabled. Because the path filled in this text widget is local, it would be nice if there would be simple validation of existence of directory described in this text widget.
Second point: validation message shown in header for empty source path is same as for the pod path "Please provide a path to deploy to on the pod.", what is not correct. This message should be different.
Third point: it would be nice to have an asterisks on required fields, such as pod or source path.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-19975) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19975?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19975:
-------------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.x)
> v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19975
> URL: https://issues.jboss.org/browse/JBIDE-19975
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: edit-template-parameter-value.png, required-value-decoration.png
>
>
> # ASSERT: make sure that you have a connection to a v3 OpenShift server
> # EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection
> # ASSERT: new application wizard pops up, listing your project
> # EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next"
> # EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit"
> # ASSERT: editing dialog pops up
> Result:
> !edit-template-parameter-value.png!
> "OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value?
> # EXEC: provide some value and back in the wizard page hit "Next"
> # ASSERT: "Resource Labels" page shows up.
> # EXEC: Hit "Add"
> # ASSERT: dialog pops up so that I can create a new label
> Result:
> !required-value-decoration.png!
> The dialog decorates missing values with a red error marker.
> In OpenShift tooling we usually use "*" when required values are missing, not the error icon.
> Notice also the 2 additional error-decorations that are shown (there are 4 error decorations while we should have 2 only)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21384) Syntax errors reported on feedhenry.js file
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21384?page=com.atlassian.jira.plugi... ]
Karel Piwko commented on JBIDE-21384:
-------------------------------------
[~akazakov] duplicate of which issue? Thanks!
> Syntax errors reported on feedhenry.js file
> -------------------------------------------
>
> Key: JBIDE-21384
> URL: https://issues.jboss.org/browse/JBIDE-21384
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.2.3.Final
> Environment: JBDS 9.0.0
> FeedHenry Cordova Light App with Ionic
> Mac OS X 10.11
> Reporter: Karel Piwko
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha1
>
> Attachments: feedhenry.js, Screen Shot 2015-12-23 at 19.00.36.png
>
>
> When a FeedHenry Cordova project is imported into JBDS, it reports 89 errors in JBDS in feedhenry.js file.
> {code}
> Description Resource Path Location Type
> Syntax error on token ":", = expected feedhenry.js /HelloCordova/www line 4099 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3475 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3499 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3512 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3694 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3752 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3906 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3916 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3958 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4030 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4042 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4063 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4076 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4213 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4274 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4777 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 8647 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10325 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10352 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10430 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10439 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10454 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10545 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10556 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10564 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10590 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3471 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3608 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3625 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3667 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3680 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3733 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3772 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3833 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3843 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3866 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4017 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4038 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4050 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4058 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4210 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4211 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4217 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4260 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4266 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4702 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4709 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4752 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4765 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6007 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6014 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6024 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6353 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10220 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10272 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10345 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10381 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10390 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10397 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10404 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10419 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10428 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10437 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10449 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3697 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3907 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3907 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3960 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4108 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4110 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4261 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4780 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4783 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4783 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4783 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 6354 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 8649 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10586 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "else BlockStatement" to complete IfStatement feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> The left-hand side of an assignment must be a variable feedhenry.js /HelloCordova/www line 1 JavaScript Problem
> The left-hand side of an assignment must be a variable feedhenry.js /HelloCordova/www line 3400 JavaScript Problem
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21408) JBDS frozen and CPU at 100% after running overnight
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21408?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21408:
---------------------------------------
BTW, I still have the Eclipse instance running (it's only taking 100% on one CPU core, so it's not even causing the fans to spin), in case I can try something else to get more information.
> JBDS frozen and CPU at 100% after running overnight
> ---------------------------------------------------
>
> Key: JBIDE-21408
> URL: https://issues.jboss.org/browse/JBIDE-21408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Attachments: frozen_jbds_jstack.txt
>
>
> Yesterday I kept JBDS 9.1.0.Beta1 running on my laptop (OS X) and I locked the laptop when I left the office. I couldn't find any Wake entries in the logs, so I think it did not sleep, but I'm not 100% sure.
> Today when I unlocked my laptop, the JBDS icon jumped in the Dock, meaning there was some pop up or something, but from then, the app is frozen and takes 100% CPU.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21408) JBDS frozen and CPU at 100% after running overnight
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21408?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21408:
--------------------------------------
Assignee: Snjezana Peco
[~snjeza] could you please take a look?
> JBDS frozen and CPU at 100% after running overnight
> ---------------------------------------------------
>
> Key: JBIDE-21408
> URL: https://issues.jboss.org/browse/JBIDE-21408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Attachments: frozen_jbds_jstack.txt
>
>
> Yesterday I kept JBDS 9.1.0.Beta1 running on my laptop (OS X) and I locked the laptop when I left the office. I couldn't find any Wake entries in the logs, so I think it did not sleep, but I'm not 100% sure.
> Today when I unlocked my laptop, the JBDS icon jumped in the Dock, meaning there was some pop up or something, but from then, the app is frozen and takes 100% CPU.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21408) JBDS frozen and CPU at 100% after running overnight
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21408?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21408:
-----------------------------------
Component/s: upstream
> JBDS frozen and CPU at 100% after running overnight
> ---------------------------------------------------
>
> Key: JBIDE-21408
> URL: https://issues.jboss.org/browse/JBIDE-21408
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Attachments: frozen_jbds_jstack.txt
>
>
> Yesterday I kept JBDS 9.1.0.Beta1 running on my laptop (OS X) and I locked the laptop when I left the office. I couldn't find any Wake entries in the logs, so I think it did not sleep, but I'm not 100% sure.
> Today when I unlocked my laptop, the JBDS icon jumped in the Dock, meaning there was some pop up or something, but from then, the app is frozen and takes 100% CPU.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months