February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12567) Upgrade PicketLink from 2.5.5.SP12-redhat-00006 to 2.5.5.SP12-redhat-00009

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12567?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12567: ------------------------------------ Fix Version/s: 19.0.0.Beta3 (was: 19.0.0.Beta2) > Upgrade PicketLink from 2.5.5.SP12-redhat-00006 to 2.5.5.SP12-redhat-00009 > -------------------------------------------------------------------------- > > Key: WFLY-12567 > URL: https://issues.redhat.com/browse/WFLY-12567 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > Fix For: 19.0.0.Beta3 > > > Branch: https://github.com/jbossas/redhat-picketlink/tree/2.5.5.SP -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12625) WildFly 19 release graphic

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12625?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12625: ------------------------------------ Fix Version/s: 19.0.0.Beta3 (was: 19.0.0.Beta2) > WildFly 19 release graphic > -------------------------- > > Key: WFLY-12625 > URL: https://issues.redhat.com/browse/WFLY-12625 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Brian Stansberry > Assignee: James Perkins > Priority: Blocker > Fix For: 19.0.0.Beta3 > > > Get a graphic for wildfly.org for the 19 release. > I put this as a Blocker for the beta, but it really blocks the Final. But might as well get it done in advance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3339) refactor the PMML regression model to use an external library for regressions

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-3339?page=com.atlassian.jira.plug... ] Gabriele Cardosi commented on DROOLS-3339: ------------------------------------------ [~jpetrlik] [~tirelli] [~dzonca] I've just started working at this refactoring with the new architecture (see https://issues.redhat.com/browse/DROOLS-4933) > refactor the PMML regression model to use an external library for regressions > ----------------------------------------------------------------------------- > > Key: DROOLS-3339 > URL: https://issues.redhat.com/browse/DROOLS-3339 > Project: Drools > Issue Type: Feature Request > Components: PMML > Affects Versions: 7.14.0.Final > Reporter: Michael McCune > Assignee: Gabriele Cardosi > Priority: Critical > Labels: PMMLRefactor, TrustyAI > > Replace the current DRL generation for regression calculation by a specialized regression library, in order to simplify the code and improve compilation and runtime performance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3339) refactor the PMML regression model to use an external library for regressions

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-3339?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-3339: ------------------------------------- Labels: PMMLRefactor TrustyAI (was: PMMLRefactor) > refactor the PMML regression model to use an external library for regressions > ----------------------------------------------------------------------------- > > Key: DROOLS-3339 > URL: https://issues.redhat.com/browse/DROOLS-3339 > Project: Drools > Issue Type: Feature Request > Components: PMML > Affects Versions: 7.14.0.Final > Reporter: Michael McCune > Assignee: Gabriele Cardosi > Priority: Critical > Labels: PMMLRefactor, TrustyAI > > Replace the current DRL generation for regression calculation by a specialized regression library, in order to simplify the code and improve compilation and runtime performance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5022) Highlight better that expression and graphical collection editor are different

by Stetson Robinson (Jira)

[ https://issues.redhat.com/browse/DROOLS-5022?page=com.atlassian.jira.plug... ] Stetson Robinson commented on DROOLS-5022: ------------------------------------------ [~uxdlc], I'd need to look at the workflow more closely for more context toward additional tool tip text, but for the radio buttons, I like your suggestions. Makes sense to me, based on the description above. [~kaldesai], would you mind digging into the context of this a bit more and sharing your suggestions on the tool-tip text and radio button options? It's related to test scenarios. Thanks. > Highlight better that expression and graphical collection editor are different > ------------------------------------------------------------------------------ > > Key: DROOLS-5022 > URL: https://issues.redhat.com/browse/DROOLS-5022 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Elizabeth Clayton > Assignee: Yeser Amer > Priority: Minor > Labels: UX, drools-tools > Attachments: collection2.png > > > Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698 > We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom. > Suggested solution: > - to explain the difference directly in the popup, somewhere close to radio buttons create/define. > Note - How it works now: > Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?" > What expression should be to make test pass: > (2 in ?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5032) [DMN Designer] Add support for (un)marshalling disconnected connections

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5032?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5032: ---------------------------------------- [~tari_manga] Understood :-) > [DMN Designer] Add support for (un)marshalling disconnected connections > ----------------------------------------------------------------------- > > Key: DROOLS-5032 > URL: https://issues.redhat.com/browse/DROOLS-5032 > Project: Drools > Issue Type: Bug > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Connections leading 'nowhere' are lost after save and reopen the diagram. > It is possible to have either the _start_ (source node) or _end_ (target node) of a connection "disconnected" i.e. not attached to a node. > The DMN (un)marshaller needs to support this (as per the narrative below). The client-side (un)marshaller also needs to support it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5032) [DMN Designer] Add support for (un)marshalling disconnected connections

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5032?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5032: ---------------------------------------- Based on the updated Description, to be clear: the model will be NOT valid, but that is the desired conscious decision as priority is given to _persisting_ the Edge anyway. > [DMN Designer] Add support for (un)marshalling disconnected connections > ----------------------------------------------------------------------- > > Key: DROOLS-5032 > URL: https://issues.redhat.com/browse/DROOLS-5032 > Project: Drools > Issue Type: Bug > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Connections leading 'nowhere' are lost after save and reopen the diagram. > It is possible to have either the _start_ (source node) or _end_ (target node) of a connection "disconnected" i.e. not attached to a node. > The DMN (un)marshaller needs to support this (as per the narrative below). The client-side (un)marshaller also needs to support it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5032) [DMN Designer] Add support for (un)marshalling disconnected connections

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5032?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5032: ---------------------------------------- Yes, thank-you [~tari_manga] your guidance helps a lot. > [DMN Designer] Add support for (un)marshalling disconnected connections > ----------------------------------------------------------------------- > > Key: DROOLS-5032 > URL: https://issues.redhat.com/browse/DROOLS-5032 > Project: Drools > Issue Type: Bug > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Connections leading 'nowhere' are lost after save and reopen the diagram. > It is possible to have either the _start_ (source node) or _end_ (target node) of a connection "disconnected" i.e. not attached to a node. > The DMN (un)marshaller needs to support this (as per the narrative below). The client-side (un)marshaller also needs to support it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5032) [DMN Designer] Add support for (un)marshalling disconnected connections

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5032?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5032: ----------------------------------- Description: Connections leading 'nowhere' are lost after save and reopen the diagram. It is possible to have either the _start_ (source node) or _end_ (target node) of a connection "disconnected" i.e. not attached to a node. The DMN (un)marshaller needs to support this (as per the narrative below). The client-side (un)marshaller also needs to support it. was:Connections leading 'nowhere' are lost after save and reopen the diagram. > [DMN Designer] Add support for (un)marshalling disconnected connections > ----------------------------------------------------------------------- > > Key: DROOLS-5032 > URL: https://issues.redhat.com/browse/DROOLS-5032 > Project: Drools > Issue Type: Bug > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Connections leading 'nowhere' are lost after save and reopen the diagram. > It is possible to have either the _start_ (source node) or _end_ (target node) of a connection "disconnected" i.e. not attached to a node. > The DMN (un)marshaller needs to support this (as per the narrative below). The client-side (un)marshaller also needs to support it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5032) Can not create connection 'nowhere'

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5032?page=com.atlassian.jira.plug... ] Michael Anstis moved JBPM-9022 to DROOLS-5032: ---------------------------------------------- Project: Drools (was: jBPM) Key: DROOLS-5032 (was: JBPM-9022) Affects Version/s: 7.33.0.Final (was: 7.33.0.Final) > Can not create connection 'nowhere' > ----------------------------------- > > Key: DROOLS-5032 > URL: https://issues.redhat.com/browse/DROOLS-5032 > Project: Drools > Issue Type: Bug > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Connections leading 'nowhere' are lost after save and reopen the diagram. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 February 2020