December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4723) Scenario is not closed after deleting

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4723?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4723: ------------------------------- Sprint: 2019 Week 50-52 (from Dec 9) > Scenario is not closed after deleting > ------------------------------------- > > Key: DROOLS-4723 > URL: https://issues.redhat.com/browse/DROOLS-4723 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: ScenarioSimulation > Attachments: delete.webm > > > See the attached video. The Scenario designer is not closed after file deletion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4723) Scenario is not closed after deleting

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4723?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4723: ------------------------------------ [~jomarko] Hi Jozef, it doesn't reproduce anymore, can you please check it? Thanks! > Scenario is not closed after deleting > ------------------------------------- > > Key: DROOLS-4723 > URL: https://issues.redhat.com/browse/DROOLS-4723 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: delete.webm > > > See the attached video. The Scenario designer is not closed after file deletion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4723) Scenario is not closed after deleting

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4723?page=com.atlassian.jira.plug... ] Yeser Amer edited comment on DROOLS-4723 at 12/9/19 8:11 AM: ------------------------------------------------------------- [~jomarko] Hi Jozef, it doesn't reproduce anymore with current master version, can you please check it? Thanks! was (Author: yamer): [~jomarko] Hi Jozef, it doesn't reproduce anymore, can you please check it? Thanks! > Scenario is not closed after deleting > ------------------------------------- > > Key: DROOLS-4723 > URL: https://issues.redhat.com/browse/DROOLS-4723 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: delete.webm > > > See the attached video. The Scenario designer is not closed after file deletion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4723) Scenario is not closed after deleting

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4723?page=com.atlassian.jira.plug... ] Yeser Amer reassigned DROOLS-4723: ---------------------------------- Assignee: Jozef Marko (was: Gabriele Cardosi) > Scenario is not closed after deleting > ------------------------------------- > > Key: DROOLS-4723 > URL: https://issues.redhat.com/browse/DROOLS-4723 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: ScenarioSimulation > Attachments: delete.webm > > > See the attached video. The Scenario designer is not closed after file deletion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4859) Document Lambda Materialization

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4859: ------------------------------------ Summary: Document Lambda Materialization Key: DROOLS-4859 URL: https://issues.redhat.com/browse/DROOLS-4859 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4855) Add PackageModel.getQueriesInRuleUnit(String simpleName)

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4855?page=com.atlassian.jira.plug... ] Edoardo Vacchi updated DROOLS-4855: ----------------------------------- Fix Version/s: 7.31.0.Final > Add PackageModel.getQueriesInRuleUnit(String simpleName) > -------------------------------------------------------- > > Key: DROOLS-4855 > URL: https://issues.redhat.com/browse/DROOLS-4855 > Project: Drools > Issue Type: Patch > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > Fix For: 7.31.0.Final > > > add getter for usage with RuleUnitDescription API, simple strings -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1400) Release tag does not confirm with release name

by Jan Stourac (Jira)

[ https://issues.redhat.com/browse/JBJCA-1400?page=com.atlassian.jira.plugi... ] Jan Stourac updated JBJCA-1400: ------------------------------- Description: Affected release is `ironjacamar-1.4.19.Final`, see https://github.com/ironjacamar/ironjacamar. There is a discrepancy between current tag name {{ironjacamar-1.4.19-Final}} and actual release name {{ironjacamar-1.4.19.Final}}. The difference is in the `-` vs `.` character right before `Final` suffix. Based on historic data correct character is `.`. Is it possible to rename/update/create correct tag name for this release? This may break automation to somebody... Would be nice to use same tag name pattern for all releases in consistency. was: Affected release is `ironjacamar-1.4.19.Final`. There is a discrepancy between current tag name {{ironjacamar-1.4.19-Final}} and actual release name {{ironjacamar-1.4.19.Final}}. The difference is in the `-` vs `.` character right before `Final` suffix. Based on historic data correct character is `.`. Is it possible to rename/update/create correct tag name for this release? This may break automation to somebody... Would be nice to use same tag name pattern for all releases in consistency. > Release tag does not confirm with release name > ---------------------------------------------- > > Key: JBJCA-1400 > URL: https://issues.redhat.com/browse/JBJCA-1400 > Project: IronJacamar > Issue Type: Bug > Components: Build > Reporter: Jan Stourac > Assignee: Stefano Maestri > Priority: Trivial > > Affected release is `ironjacamar-1.4.19.Final`, see https://github.com/ironjacamar/ironjacamar. > There is a discrepancy between current tag name {{ironjacamar-1.4.19-Final}} and actual release name {{ironjacamar-1.4.19.Final}}. The difference is in the `-` vs `.` character right before `Final` suffix. Based on historic data correct character is `.`. > Is it possible to rename/update/create correct tag name for this release? > This may break automation to somebody... Would be nice to use same tag name pattern for all releases in consistency. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1911) Allow lazy initialization of SSLContext inside OAuth2IntrospectValidator

by Loïc Mathieu (Jira)

[ https://issues.redhat.com/browse/ELY-1911?page=com.atlassian.jira.plugin.... ] Loïc Mathieu closed ELY-1911. ----------------------------- Resolution: Won't Do No more needed ,we found a workaround at our side. > Allow lazy initialization of SSLContext inside OAuth2IntrospectValidator > ------------------------------------------------------------------------ > > Key: ELY-1911 > URL: https://issues.redhat.com/browse/ELY-1911 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Mechanisms > Affects Versions: 2.0.0.Alpha4 > Reporter: Loïc Mathieu > Priority: Major > > Quarkus uses GraalVM static initialization capability to perform native image optimization during the build of a native image. > Quarkus uses wildfly-elytron-realm-token library to implements OAuth2 authentication, in this library the OAuth2IntrospectValidator needs an initialized SSLContext at class initialization time (inside it's constructor), but GraalVM forbid to instantiate an SSLContext at static initilization time (it should not be present in the snapshoted heap). > I propose to allow a lazily initialization of the SSLContext in case no SSLContext is provided to OAuth2IntrospectValidator, this will allow to workaround the issue in native mode. > You can follow this discussion on the Quarkus side with a proposed implementation: https://github.com/quarkusio/quarkus/pull/5768 > I can propose a PR on wildfly-elytron with a fix. This will slightly modify the current behaviour as it will no longuer be necessary to provide a SSLContext: if none is provided we will use the default one. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1400) Release tag does not confirm with release name

by Jan Stourac (Jira)

[ https://issues.redhat.com/browse/JBJCA-1400?page=com.atlassian.jira.plugi... ] Jan Stourac commented on JBJCA-1400: ------------------------------------ [~maeste] - this issue has been created as unassigned. I saw you were the one who reviewed my last contribution to this repository so I assigned this to you. Feel free to unassign or reassign if this was inappropriate move from my side :) Thanks! > Release tag does not confirm with release name > ---------------------------------------------- > > Key: JBJCA-1400 > URL: https://issues.redhat.com/browse/JBJCA-1400 > Project: IronJacamar > Issue Type: Bug > Components: Build > Reporter: Jan Stourac > Assignee: Stefano Maestri > Priority: Trivial > > Affected release is `ironjacamar-1.4.19.Final`. > There is a discrepancy between current tag name {{ironjacamar-1.4.19-Final}} and actual release name {{ironjacamar-1.4.19.Final}}. The difference is in the `-` vs `.` character right before `Final` suffix. Based on historic data correct character is `.`. > Is it possible to rename/update/create correct tag name for this release? > This may break automation to somebody... Would be nice to use same tag name pattern for all releases in consistency. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1400) Release tag does not confirm with release name

by Jan Stourac (Jira)

[ https://issues.redhat.com/browse/JBJCA-1400?page=com.atlassian.jira.plugi... ] Jan Stourac reassigned JBJCA-1400: ---------------------------------- Assignee: Stefano Maestri > Release tag does not confirm with release name > ---------------------------------------------- > > Key: JBJCA-1400 > URL: https://issues.redhat.com/browse/JBJCA-1400 > Project: IronJacamar > Issue Type: Bug > Components: Build > Reporter: Jan Stourac > Assignee: Stefano Maestri > Priority: Trivial > > Affected release is `ironjacamar-1.4.19.Final`. > There is a discrepancy between current tag name {{ironjacamar-1.4.19-Final}} and actual release name {{ironjacamar-1.4.19.Final}}. The difference is in the `-` vs `.` character right before `Final` suffix. Based on historic data correct character is `.`. > Is it possible to rename/update/create correct tag name for this release? > This may break automation to somebody... Would be nice to use same tag name pattern for all releases in consistency. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019