[JBoss JIRA] (LOGMGR-264) Allow logger nodes to be used on different log contexts
by James Perkins (Jira)
[ https://issues.redhat.com/browse/LOGMGR-264?page=com.atlassian.jira.plugi... ]
James Perkins updated LOGMGR-264:
---------------------------------
Fix Version/s: 2.2.0.Final
3.0.0.Final
> Allow logger nodes to be used on different log contexts
> -------------------------------------------------------
>
> Key: LOGMGR-264
> URL: https://issues.redhat.com/browse/LOGMGR-264
> Project: JBoss Log Manager
> Issue Type: Enhancement
> Components: core
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Fix For: 2.2.0.Final, 3.0.0.Final
>
>
> Currently logger nodes belong to a single log context. This means that shared classes with static loggers are created on the log context that initializes the class. It would be useful if static loggers on shared classes could log to different log contexts.
> The concept would be something of a switchable log context for a logger. This would be based on the TCCL and the class loader needs to be registered in order to enable this functionality.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (LOGMGR-264) Allow logger nodes to be used on different log contexts
by James Perkins (Jira)
[ https://issues.redhat.com/browse/LOGMGR-264?page=com.atlassian.jira.plugi... ]
James Perkins updated LOGMGR-264:
---------------------------------
Issue Type: Feature Request (was: Enhancement)
> Allow logger nodes to be used on different log contexts
> -------------------------------------------------------
>
> Key: LOGMGR-264
> URL: https://issues.redhat.com/browse/LOGMGR-264
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Components: core
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Fix For: 2.2.0.Final, 3.0.0.Final
>
>
> Currently logger nodes belong to a single log context. This means that shared classes with static loggers are created on the log context that initializes the class. It would be useful if static loggers on shared classes could log to different log contexts.
> The concept would be something of a switchable log context for a logger. This would be based on the TCCL and the class loader needs to be registered in order to enable this functionality.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFCORE-4791) HttpManagementConstantHeadersTestCase causes tests failures
by Richard Opalka (Jira)
[ https://issues.redhat.com/browse/WFCORE-4791?page=com.atlassian.jira.plug... ]
Richard Opalka commented on WFCORE-4791:
----------------------------------------
With the PR applied I was not able to reproduce the problem locally [~tterem]
> HttpManagementConstantHeadersTestCase causes tests failures
> -----------------------------------------------------------
>
> Key: WFCORE-4791
> URL: https://issues.redhat.com/browse/WFCORE-4791
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Reporter: Richard Opalka
> Assignee: Tomas Terem
> Priority: Major
> Fix For: 11.0.0.Beta8
>
> Attachments: testsuite.log
>
>
> Commit 68928b0b in WildFly-Core introduced new regression.
> High probably test doesn't do proper test environment clean up
> and some tests following it are thus failing. The issue isn't visible
> in our CI environment so it probably depends on actual tests ordering.
> I am able to reproduce this issue on my laptop always.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4966) [DMN Designer] Dragging a field at the bottom of type designer
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-4966?page=com.atlassian.jira.plug... ]
Michael Anstis updated DROOLS-4966:
-----------------------------------
Tester: Jozef Marko
> [DMN Designer] Dragging a field at the bottom of type designer
> ---------------------------------------------------------------
>
> Key: DROOLS-4966
> URL: https://issues.redhat.com/browse/DROOLS-4966
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.32.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: drag-2.gif
>
>
> - add several fields/structures so that the list exceeds the viewport
> - scroll down to the bottom of the editor
> - try dragging the bottom field
> - the view does not scroll, but the field will jump "up" at seemingly random positions at the top
> it's nearly impossible to reorder a field when it's at the bottom
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4965) [DMN Designer] Dragged structure fields nest in a counterintuitive way
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-4965?page=com.atlassian.jira.plug... ]
Michael Anstis updated DROOLS-4965:
-----------------------------------
Tester: Jozef Marko
> [DMN Designer] Dragged structure fields nest in a counterintuitive way
> ----------------------------------------------------------------------
>
> Key: DROOLS-4965
> URL: https://issues.redhat.com/browse/DROOLS-4965
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.32.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: drag-1.gif
>
>
> Because the handle is aligned leftmost, I tend to keep it aligned to the left;
> but this causes the field to be "unnested" and moved to toplevel.
> I suggest to draw the handle aligned to label, instead of the border, suggesting that drag has to start from that point
> !drag-1.gif!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4965) [DMN Designer] Dragged structure fields nest in a counterintuitive way
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-4965?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-4965:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Dragged structure fields nest in a counterintuitive way
> ----------------------------------------------------------------------
>
> Key: DROOLS-4965
> URL: https://issues.redhat.com/browse/DROOLS-4965
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.32.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: drag-1.gif
>
>
> Because the handle is aligned leftmost, I tend to keep it aligned to the left;
> but this causes the field to be "unnested" and moved to toplevel.
> I suggest to draw the handle aligned to label, instead of the border, suggesting that drag has to start from that point
> !drag-1.gif!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4966) [DMN Designer] Dragging a field at the bottom of type designer
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-4966?page=com.atlassian.jira.plug... ]
Michael Anstis reassigned DROOLS-4966:
--------------------------------------
Assignee: Guilherme Gomes (was: Michael Anstis)
> [DMN Designer] Dragging a field at the bottom of type designer
> ---------------------------------------------------------------
>
> Key: DROOLS-4966
> URL: https://issues.redhat.com/browse/DROOLS-4966
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.32.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: drag-2.gif
>
>
> - add several fields/structures so that the list exceeds the viewport
> - scroll down to the bottom of the editor
> - try dragging the bottom field
> - the view does not scroll, but the field will jump "up" at seemingly random positions at the top
> it's nearly impossible to reorder a field when it's at the bottom
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-4963) [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-4963?page=com.atlassian.jira.plug... ]
Michael Anstis commented on DROOLS-4963:
----------------------------------------
[~evacchi] Both your screenshots seem identical!!? Or I am missing some detail?
I tried to replicate something, any strange behaviour, but was unable to see any save/cancel buttons appearing/disappearing.
Could you please provide a (corrected) second screenshot or more narrative?
> [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4963
> URL: https://issues.redhat.com/browse/DROOLS-4963
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.32.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2020-01-22 16-16-29.png, Screenshot from 2020-01-22 16-16-29.png
>
>
> hiding the inspector on the right-hand side uncovers the save/cancel buttons
> !Screenshot from 2020-01-22 16-16-29.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months