[Red Hat JIRA] (WFCORE-5264) Update all projects with a dependency on wildfly-elytron to use individual modules.
by Darran Lofthouse (Jira)
Darran Lofthouse created WFCORE-5264:
----------------------------------------
Summary: Update all projects with a dependency on wildfly-elytron to use individual modules.
Key: WFCORE-5264
URL: https://issues.redhat.com/browse/WFCORE-5264
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 15.0.0.Beta1
By doing this we will have a much better record of which areas of WildFly Elytron are used by which components in the application server.
We should be cautious to avoid any transitive dependencies.
This task is only to look at the Maven dependencies, the modules should also be looked at later if we decide it is appropriate.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (WFCORE-5263) Update all projects with a dependency on wildfly-elytron to use individual modules.
by Darran Lofthouse (Jira)
Darran Lofthouse created WFCORE-5263:
----------------------------------------
Summary: Update all projects with a dependency on wildfly-elytron to use individual modules.
Key: WFCORE-5263
URL: https://issues.redhat.com/browse/WFCORE-5263
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 15.0.0.Beta1
By doing this we will have a much better record of which areas of WildFly Elytron are used by which components in the application server.
We should be cautious to avoid any transitive dependencies.
This task is only to look at the Maven dependencies, the modules should also be looked at later if we decide it is appropriate.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (DROOLS-5977) [DMN Editor] A nested Structure with no fields breaks the Decision Table Editor
by Edoardo Vacchi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5977?page=com.atlassian.jira.plug... ]
Edoardo Vacchi updated DROOLS-5977:
-----------------------------------
Description:
When a field of type Structure is added with no sub-fields in the data type editor, and a Decision Table for that type is created, then the type that shows up in the Decision Table bears the name of the structure, which is incorrect (see video)
The video also shows how this may happen by mistake.
was:When a field of type Structure is added with no sub-fields in the data type editor, and a Decision Table for that type is created, then the type that shows up in the Decision Table bears the name of the structure, which is incorrect (see video)
> [DMN Editor] A nested Structure with no fields breaks the Decision Table Editor
> -------------------------------------------------------------------------------
>
> Key: DROOLS-5977
> URL: https://issues.redhat.com/browse/DROOLS-5977
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.49.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Guilherme Gomes
> Priority: Major
> Attachments: nested-structure.webm
>
>
> When a field of type Structure is added with no sub-fields in the data type editor, and a Decision Table for that type is created, then the type that shows up in the Decision Table bears the name of the structure, which is incorrect (see video)
> The video also shows how this may happen by mistake.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (DROOLS-5977) [DMN Editor] A nested Structure with no fields breaks the Decision Table Editor
by Edoardo Vacchi (Jira)
Edoardo Vacchi created DROOLS-5977:
--------------------------------------
Summary: [DMN Editor] A nested Structure with no fields breaks the Decision Table Editor
Key: DROOLS-5977
URL: https://issues.redhat.com/browse/DROOLS-5977
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.49.0.Final
Reporter: Edoardo Vacchi
Assignee: Guilherme Gomes
When a field of type Structure is added with no sub-fields in the data type editor, and a Decision Table for that type is created, then the type that shows up in the Decision Table bears the name of the structure, which is incorrect (see video)
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months
[Red Hat JIRA] (DROOLS-5976) [DMN Editor] Reordering non-Structure types may cause conversion to Structure
by Edoardo Vacchi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5976?page=com.atlassian.jira.plug... ]
Edoardo Vacchi updated DROOLS-5976:
-----------------------------------
Attachment: reorder.webm
reorder-2.webm
Steps to Reproduce:
- Create a structure
- Add a field of any non-Structure type (e.g. String)
- Add a field of another non-Structure type (e.g. number)
- Drag the number field down
-> if you keep the field aligned to the margin, it will nest under its immediate sibling, turning it into a Structure
-> if you keep it closer to the center (which IMO would suggest nesting) it's instead treated as a sibling
I understand this is probably intended behavior, but IMO it is confusing
Expected: if you drag a field over a non-Structure field, I would expect such non-Structure field NOT to be converted into a Structure, and thus NOT nest the field you are dragging under it
Workaround: Workaround Exists
Workaround Description: drag fields while keeping the mouse close to the middle of other fields
> [DMN Editor] Reordering non-Structure types may cause conversion to Structure
> -----------------------------------------------------------------------------
>
> Key: DROOLS-5976
> URL: https://issues.redhat.com/browse/DROOLS-5976
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.49.0.Final
> Reporter: Edoardo Vacchi
> Assignee: Guilherme Gomes
> Priority: Major
> Attachments: reorder-2.webm, reorder.webm
>
>
> Reordering fields is a bit error prone, one shaky hand may result in changing the type of a field to Structure.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 2 months