December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-203) Intoduce usage of Regression bugzilla keyword

by Filip Brychta (JIRA)

Filip Brychta created HAWKULARQE-203: ---------------------------------------- Summary: Intoduce usage of Regression bugzilla keyword Key: HAWKULARQE-203 URL: https://issues.jboss.org/browse/HAWKULARQE-203 Project: Hawkular QE Issue Type: Task Reporter: Filip Brychta Assignee: Michael Foley Priority: Critical We need to introduce Regression bugzilla keyword to our workflow. This keyword should be used in cases when some already working feature delivered to customers is broken. All issues with this keyword must be fixed before the release -> everything which was working before should be working in newer version too. Following should be done: * introduce the usage to our bugzilla workflow document * notify the whole team (including dev) to start using it * prepare bugzilla query which will list all open issues with this keyword and share it with the team -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3442) CLI can't reload if authentication configuration changed

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3442?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3442: ----------------------------------------- Description: The context: - Legacy ManagementRealm, no local-auth enabled, only users located properties file. - SASL authentication factory, digest with FooRealm, userName/password in other properties file The http management interface - Reference ManagementRealm and upgrade references SAL factory. >From CLI: 1) User connects using credentials required for FooRealm 2) User disables SASL authentication : /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory,value=undefined 3) User reloads ==> Connection fails. The user should be prompted for ManagementRealm credentials (if the current ones are not valid in the context of this realm). was: The context: - Legacy ManagementRealm, no local-auth enabled, only users located properties file. - SASL authentication factory, digest with FooRealm, userName/password in other properties file The http management interface - Reference ManagementRealm and upgrade references SAL factory. >From CLI: 1) User connects using credentials required for FooRealm 2) User disables SASL authentication : /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory,value=undefined 3) User reloads ==> Connection fails. The user should be prompted for ManagementRealm credentials (if the current ones are not valid in the context of this realm). Furthermore, ConnectionInfo should expose the realm the CLI is connected to. > CLI can't reload if authentication configuration changed > -------------------------------------------------------- > > Key: WFCORE-3442 > URL: https://issues.jboss.org/browse/WFCORE-3442 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > The context: > - Legacy ManagementRealm, no local-auth enabled, only users located properties file. > - SASL authentication factory, digest with FooRealm, userName/password in other properties file > The http management interface > - Reference ManagementRealm and upgrade references SAL factory. > From CLI: > 1) User connects using credentials required for FooRealm > 2) User disables SASL authentication : /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory,value=undefined > 3) User reloads ==> Connection fails. > The user should be prompted for ManagementRealm credentials (if the current ones are not valid in the context of this realm). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3443) CLI ConnectionInfo should expose security realm.

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-3443: -------------------------------------------- Summary: CLI ConnectionInfo should expose security realm. Key: WFCORE-3443 URL: https://issues.jboss.org/browse/WFCORE-3443 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise This would allow to identify the authentication context the user is bound to. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2131) [DMN Editor] Boxed Expressions: Invocation editor

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2131?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2131: ----------------------------------- Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50 (was: 2017 Week 45-46, 2017 Week 47-48) > [DMN Editor] Boxed Expressions: Invocation editor > ------------------------------------------------- > > Key: DROOLS-2131 > URL: https://issues.jboss.org/browse/DROOLS-2131 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2132) [DMN Editor] Boxed Expressions: FunctionDefinition editor

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2132?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2132: ----------------------------------- Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50 (was: 2017 Week 45-46, 2017 Week 47-48) > [DMN Editor] Boxed Expressions: FunctionDefinition editor > --------------------------------------------------------- > > Key: DROOLS-2132 > URL: https://issues.jboss.org/browse/DROOLS-2132 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2136) Remove not used mvn dependencies

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2136?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2136: ----------------------------------- Sprint: 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50 (was: 2017 Week 45-46, 2017 Week 47-48) > Remove not used mvn dependencies > -------------------------------- > > Key: DROOLS-2136 > URL: https://issues.jboss.org/browse/DROOLS-2136 > Project: Drools > Issue Type: Task > Affects Versions: 7.4.1.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > > In the drools-wb repository, remove all mvn dependencies that > {code:mvn} > mvn dependency:analyze > {code} > marks as declared but not used -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1767) FEEL: add compile-time cycle detection

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1767?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1767: ----------------------------------- Sprint: 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50 (was: 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48) > FEEL: add compile-time cycle detection > --------------------------------------- > > Key: DROOLS-1767 > URL: https://issues.jboss.org/browse/DROOLS-1767 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.4.1.Final > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Priority: Minor > > Similar to what's done in https://issues.jboss.org/browse/DROOLS-1730 but during validation stage -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1770) More FEEL runtime cycle detection tests

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1770?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1770: ----------------------------------- Sprint: 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50 (was: 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48) > More FEEL runtime cycle detection tests > --------------------------------------- > > Key: DROOLS-1770 > URL: https://issues.jboss.org/browse/DROOLS-1770 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.4.1.Final > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Priority: Minor > > Runtime cycle detecton lacks tests for false positive, such as deadly diamond topology: > A depends on B and C > B and C depend on D -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2109) [XLS Decision Table] New Asset Dialogue misses descriptions

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2109?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2109: ----------------------------------- Sprint: 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50 (was: 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48) > [XLS Decision Table] New Asset Dialogue misses descriptions > ----------------------------------------------------------- > > Key: DROOLS-2109 > URL: https://issues.jboss.org/browse/DROOLS-2109 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Attachments: Screenshot from 2017-11-03 10-20-21.png > > > The attached dialogue shows missing descriptions for table format and file selector. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1795) [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1795?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1795: ----------------------------------- Sprint: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50 (was: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48) > [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column. > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1795 > URL: https://issues.jboss.org/browse/DROOLS-1795 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Final > Reporter: Mark Coble > Assignee: Mark Coble > Priority: Minor > Fix For: 7.0.0.Final > > Attachments: guvnor-3507.png > > > If a condition BRL column is added to a DT with bound variables that are used in an action column and that variable name is subsequently changed, the attached error message occurs when updating the action column with the new variable name. In the attached message the original variable name is 'app'. Hitting 'ok' returns you to the DT which has actually refactored the DT with the new variable name and validation is successful. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017