January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (ELY-2076) Some traces of "programatic" remain in code that should be converted to "programmatic"

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-2076: ------------------------------------- Summary: Some traces of "programatic" remain in code that should be converted to "programmatic" Key: ELY-2076 URL: https://issues.redhat.com/browse/ELY-2076 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.15.0.CR1 These remaining misspelt instances are on internal method names and not exposed over public API. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (ELYWEB-126) Programmatic authentication is misspelt as "Programatic"

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-126?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated ELYWEB-126: ------------------------------------ Component/s: Undertow > Programmatic authentication is misspelt as "Programatic" > --------------------------------------------------------- > > Key: ELYWEB-126 > URL: https://issues.redhat.com/browse/ELYWEB-126 > Project: Elytron Web > Issue Type: Bug > Components: Undertow > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.CR1 > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (ELYWEB-126) Programmatic authentication is misspelt as "Programatic"

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-126?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated ELYWEB-126: ------------------------------------ Fix Version/s: 1.9.0.CR1 > Programmatic authentication is misspelt as "Programatic" > --------------------------------------------------------- > > Key: ELYWEB-126 > URL: https://issues.redhat.com/browse/ELYWEB-126 > Project: Elytron Web > Issue Type: Bug > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.0.CR1 > > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (ELYWEB-126) Programmatic authentication is misspelt as "Programatic"

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-126: --------------------------------------- Summary: Programmatic authentication is misspelt as "Programatic" Key: ELYWEB-126 URL: https://issues.redhat.com/browse/ELYWEB-126 Project: Elytron Web Issue Type: Bug Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5978) DMN DT Compilation NPE for not-existing typeRef

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5978: -------------------------------------- Summary: DMN DT Compilation NPE for not-existing typeRef Key: DROOLS-5978 URL: https://issues.redhat.com/browse/DROOLS-5978 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari See [DROOLS-5977] -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14377) Update all projects with a dependency on wildfly-elytron to use individual modules.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-14377?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFCORE-5264 to WFLY-14377: ------------------------------------------------- Component/s: Security (was: Security) Fix Version/s: 23.0.0.Beta1 (was: 15.0.0.Beta1) Key: WFLY-14377 (was: WFCORE-5264) Project: WildFly (was: WildFly Core) > Update all projects with a dependency on wildfly-elytron to use individual modules. > ----------------------------------------------------------------------------------- > > Key: WFLY-14377 > URL: https://issues.redhat.com/browse/WFLY-14377 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 23.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)

5 years, 2 months

1
0
0 / 0

[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)

5 years, 2 months

1
0
0 / 0

[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)

5 years, 2 months

1
0
0 / 0

[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: ----------------------------------- Attachment: nested-structure.webm > [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)

5 years, 2 months

1
0
0 / 0

[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 commented on DROOLS-5977: ---------------------------------------- [~tari_manga] > [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)

5 years, 2 months

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

jboss-jira January 2021