September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5663) fix default kie-maven-plugin for generateModel configuration flag

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5663?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5663: ----------------------------------- Steps to Reproduce: # Take the example from https://github.com/kiegroup/droolsjbpm-integration/tree/master/kie-maven-... # Remove this line from pom: https://github.com/kiegroup/droolsjbpm-integration/blob/518e387d366eba3b0... # Attach debugger from {{mvn clean install}} was: 1. Take the example from https://github.com/kiegroup/droolsjbpm-integration/tree/master/kie-maven-... 2. Remove this line from pom: https://github.com/kiegroup/droolsjbpm-integration/blob/518e387d366eba3b0... 3. Attach debugger from {{mvn clean install}} > fix default kie-maven-plugin for generateModel configuration flag > ----------------------------------------------------------------- > > Key: DROOLS-5663 > URL: https://issues.redhat.com/browse/DROOLS-5663 > Project: Drools > Issue Type: Bug > Components: integration > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5663) fix default kie-maven-plugin for generateModel configuration flag

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5663: -------------------------------------- Summary: fix default kie-maven-plugin for generateModel configuration flag Key: DROOLS-5663 URL: https://issues.redhat.com/browse/DROOLS-5663 Project: Drools Issue Type: Bug Components: integration Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5485) Move test cases from drools-compiler to drools-test-coverage

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5485?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-5485: ------------------------------------------- Let's discuss after finishing some modules de-scope. Mario seems to prefer drools-model-compiler while Tibor recommends drools-test-coverage. > Move test cases from drools-compiler to drools-test-coverage > ------------------------------------------------------------ > > Key: DROOLS-5485 > URL: https://issues.redhat.com/browse/DROOLS-5485 > Project: Drools > Issue Type: Task > Components: core engine, executable model > Affects Versions: 7.39.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Move test cases from drools-compiler to drools-test-coverage/test-compiler-integration so that we can increase the test coverage for executable-model. > At the moment, I'm not yet sure how many of the test cases can be moved. Basically DRL based test only. > Luca noted: > > there are some tests in -compiler that are not supported in the model compiler (I'm thinking about all the ASM/type generation related). That should be left in -compiler and hopefully moved outside like the traits > If we find test failures by executable-model, we would spawn new JIRAs to deal with them one-by-one. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5554) Enhance generated sources annotation for DMNTypes

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5554?page=com.atlassian.jira.plug... ] Toshiya Kobayashi closed DROOLS-5554. ------------------------------------- Resolution: Duplicate Issue Duplicate of KOGITO-2277 > Enhance generated sources annotation for DMNTypes > ------------------------------------------------- > > Key: DROOLS-5554 > URL: https://issues.redhat.com/browse/DROOLS-5554 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Add annotation to describe DMNTypes in generated sources (InputSet, OutputSet, composite types) for Swagger/OpenAPI. Especially, time related DMN types like time, duration are treated as Java interfaces like Temporal or TemporalAmount in order to accept several Java classes (for output purpose). So this kind of description is needed. > FYI) > https://github.com/kiegroup/drools/pull/2993#issuecomment-660898266 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5095) Add the ability to make use of an automatically generated self-signed certificate with Elytron

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-5095?page=com.atlassian.jira.plug... ] Farah Juma updated WFCORE-5095: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4341 > Add the ability to make use of an automatically generated self-signed certificate with Elytron > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-5095 > URL: https://issues.redhat.com/browse/WFCORE-5095 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > WFCORE-1576 added the ability to lazily generate a self-signed certificate on first use for a specified host name when using legacy security. This RFE is to provide similar functionality when Elytron is in use. Like with legacy security, it will be important to log a warning message so the user knows that a self-signed certificate is being used and to indicate that this certificate should not be used in a production environment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4132) Pure Client Side Scenario Simulation Editor

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4132?page=com.atlassian.jira.plug... ] Yeser Amer resolved DROOLS-4132. -------------------------------- Resolution: Done > Pure Client Side Scenario Simulation Editor > ------------------------------------------- > > Key: DROOLS-4132 > URL: https://issues.redhat.com/browse/DROOLS-4132 > Project: Drools > Issue Type: Epic > Reporter: Eder Ignatowicz > Assignee: Yeser Amer > Priority: Major > > The goal of this phase: Be able to have a pure client-side editor for Scenario Simulation. > The end result of this epic will be a client-side distribution of Scenario Simulation working on VSCode and able to run and show the result of the test execution. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4145) R&D how to import/export CSV inside VSCode

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4145?page=com.atlassian.jira.plug... ] Yeser Amer closed DROOLS-4145. ------------------------------ Resolution: Duplicate Issue Moved to KOGITO-3416 > R&D how to import/export CSV inside VSCode > ------------------------------------------ > > Key: DROOLS-4145 > URL: https://issues.redhat.com/browse/DROOLS-4145 > Project: Drools > Issue Type: Enhancement > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13893) Infinispan Directory Provider deprecated in Hibernate Search 6.x

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-13893: -------------------------------------- Summary: Infinispan Directory Provider deprecated in Hibernate Search 6.x Key: WFLY-13893 URL: https://issues.redhat.com/browse/WFLY-13893 Project: WildFly Issue Type: Bug Components: BOM Reporter: Eduardo Martins Assignee: Eduardo Martins Hibernate Search dependency on Infinispan-directory-provider was deprecated, and replaced by hibernate-search-backend-lucene in Hibernate Search 6.x. Infinispan is no longer releasing new versions of the directory provider too, so Jakarta EE8 BOM Builder is unable to automatically manage its version, by referring to the ISPN Core version. Till WFLY moves to Hibernate Search 6.x the BOMs should manually specify the directory provider dependency version as 10.1.8.Final, the last one managed automatically. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13892) Opentracing capability is not properly registered

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-13892: ---------------------------------------- Summary: Opentracing capability is not properly registered Key: WFLY-13892 URL: https://issues.redhat.com/browse/WFLY-13892 Project: WildFly Issue Type: Bug Components: MP OpenTracing Affects Versions: 21.0.0.Beta1 Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Currently the opentracing capability that allow other subsystems to detect the presence of the opentracing subsystem is not properly registered -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13888) Move JWTEJBTestCase to testsuite/integration/microprofile

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13888?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-13888: ------------------------------------ Fix Version/s: 21.0.0.Final > Move JWTEJBTestCase to testsuite/integration/microprofile > --------------------------------------------------------- > > Key: WFLY-13888 > URL: https://issues.redhat.com/browse/WFLY-13888 > Project: WildFly > Issue Type: Task > Components: MP JWT > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Final > > > Part of our overall testing strategy is wanting to be able to run testsuite/integration/basic using the output of the ee-build maven module or provisioning using the wildfly-ee feature pack. Having a JWT test in that testsuite breaks that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 September 2020