December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5122) SceSim is not clearing alert after update, successful Save and re Run

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5122?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5122: ---------------------------------------- As of today, sanity check for 7.47.0.Final, updating the setting and Save does not clear the previous problem once resolved. > SceSim is not clearing alert after update, successful Save and re Run > --------------------------------------------------------------------- > > Key: DROOLS-5122 > URL: https://issues.redhat.com/browse/DROOLS-5122 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Matteo Mortari > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: Screenshot 2020-03-03 at 15.36.33.png > > > as attached -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14142) Update Google guava to 30.0-jre

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/WFLY-14142?page=com.atlassian.jira.plugi... ] Boris Unckel commented on WFLY-14142: ------------------------------------- WildFly-Core has to provide model-test dependencies first. > Update Google guava to 30.0-jre > ------------------------------- > > Key: WFLY-14142 > URL: https://issues.redhat.com/browse/WFLY-14142 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch, JMS > Reporter: Boris Unckel > Assignee: Cheng Fang > Priority: Major > > Update Google guava to [30.0-jre|https://mvnrepository.com/artifact/com.google.guava/guava/30.0-jre]. Exclude all dependencies but [failureaccess 1.0.1|https://mvnrepository.com/artifact/com.google.guava/failureaccess/1...] according to [Google Guava Important Warnings #3|https://github.com/google/guava]. > [Release Notes|https://github.com/google/guava/releases/tag/v30.0] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2049) Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/ELY-2049?page=com.atlassian.jira.plugin.... ] Boris Unckel updated ELY-2049: ------------------------------ Affects Version/s: 1.13.2.Final (was: 1.13.0.CR1) > Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial > ----------------------------------------------------------------------- > > Key: ELY-2049 > URL: https://issues.redhat.com/browse/ELY-2049 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Security Manager > Affects Versions: 1.13.2.Final > Reporter: Boris Unckel > Priority: Major > > The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions. > Example: > [java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...] > line 2048 > The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs. > Current code: > {code:java} > public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) { > ProtectionDomain deniedDomain = null; > if (domains != null) for (ProtectionDomain domain : domains) { > if (! domain.implies(permission)) { > final CodeSource codeSource = domain.getCodeSource(); > final ClassLoader classLoader = domain.getClassLoader(); > final Principal[] principals = domain.getPrincipals(); > if (principals == null || principals.length == 0) { > access.accessCheckFailed(permission, codeSource, classLoader); > } else { > access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals)); > } > if (deniedDomain == null && ! LOG_ONLY) { > deniedDomain = domain; > } > } > } > return deniedDomain; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5123) SceSim editor is picking datatype from another project

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5123?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5123: ---------------------------------------- As of today, sanity check for 7.47.0.Final, the behaviour is still the same as originally reported: new proof: !Screenshot 2020-12-02 at 16.36.39.png|thumbnail! > SceSim editor is picking datatype from another project > ------------------------------------------------------ > > Key: DROOLS-5123 > URL: https://issues.redhat.com/browse/DROOLS-5123 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Matteo Mortari > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: Screenshot 2020-03-03 at 15.39.12.png, Screenshot 2020-12-02 at 16.36.39.png > > > not sure if normal, as attached. please advise -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5696) Guided Rule Editor: Call method on XYZ with formula containing quotes does not re-open correctly

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5696?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5696: -------------------------------- Tester: Jozef Marko (was: Jan Stastny) > Guided Rule Editor: Call method on XYZ with formula containing quotes does not re-open correctly > ------------------------------------------------------------------------------------------------ > > Key: DROOLS-5696 > URL: https://issues.redhat.com/browse/DROOLS-5696 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14158) Override the observability layer in the wildfly feature pack

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-14158: --------------------------------------- Summary: Override the observability layer in the wildfly feature pack Key: WFLY-14158 URL: https://issues.redhat.com/browse/WFLY-14158 Project: WildFly Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 22.0.0.Beta1 Provide a layer-spec.xml for observability in the wildfly feature pack, that will thus override what is in wildfly-ee. The meaning of observability will differ in the two as wildfly-ee will not provide the MP specs. This task is not about changing the layer; it's just to provide a file that other work can manipulate. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14142) Update Google guava to 30.0-jre

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14142?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-14142: ----------------------------------------- Hi [~xf01213] The testsuite/integration/smoke/target/wildfly/standalone/log/server.log file may provide more information. or testsuite/integration/smoke/target/surefire-reports/TEST-org.jboss.as.test.smoke.deployment.rar.tests.earmultirar.EarPackagedMultiRarDeploymentTestCase.xml. Arquillian installs it's own deployment before installing any deployment configured in the test. It's called 'arquillian-service'. Sounds like that is failing. > Update Google guava to 30.0-jre > ------------------------------- > > Key: WFLY-14142 > URL: https://issues.redhat.com/browse/WFLY-14142 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch, JMS > Reporter: Boris Unckel > Assignee: Cheng Fang > Priority: Major > Attachments: 2020-12-01_04after_guava_build.txt > > > Update Google guava to [30.0-jre|https://mvnrepository.com/artifact/com.google.guava/guava/30.0-jre]. Exclude all dependencies but [failureaccess 1.0.1|https://mvnrepository.com/artifact/com.google.guava/failureaccess/1...] according to [Google Guava Important Warnings #3|https://github.com/google/guava]. > [Release Notes|https://github.com/google/guava/releases/tag/v30.0] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5865) Folder test-classes is not excluded from kie-maven-plugin build

by Laura Cameran (Jira)

Laura Cameran created DROOLS-5865: ------------------------------------- Summary: Folder test-classes is not excluded from kie-maven-plugin build Key: DROOLS-5865 URL: https://issues.redhat.com/browse/DROOLS-5865 Project: Drools Issue Type: Bug Components: tools Affects Versions: 7.46.0.Final Reporter: Laura Cameran Assignee: Mario Fusco Maven goal kie-maven-plugin:build doesn't exclude folder "target/test-classes". As result, if we previously run for example mvn test goal, the target/test-classes folder is included during the write operation on outputDirectory. I think this issue is related to DROOLS-4440. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14085) JSF Flow TCK failures

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14085?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-14085. ------------------------------------- Fix Version/s: 22.0.0.Beta1 Assignee: Farah Juma Resolution: Done [~fjuma] [~jaslee] We're not seeing JSF failures in the EE 9 tck any more so I'll resolve this. I suspect WFLY-14109 may have fixed this. > JSF Flow TCK failures > --------------------- > > Key: WFLY-14085 > URL: https://issues.redhat.com/browse/WFLY-14085 > Project: WildFly > Issue Type: Sub-task > Components: JSF > Reporter: Jason Lee > Assignee: Farah Juma > Priority: Major > Fix For: 22.0.0.Beta1 > > > {color:#000000}[javatest.batch] Successfully undeployed app: /home/jdlee/work/ee-9-tck/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jsf/spec/flows/intermediate/jsf_flows_intermediate_web.war {color} > [javatest.batch] Undeployed apps from - /home/jdlee/work/ee-9-tck/jakartaeetck/bin/xml/../../dist/com/sun/ts/tests/jsf/spec/flows/intermediate > [javatest.batch] Successfully removed JMS connection factories from server 1. > [javatest.batch] Successfully removed JMS connection factories from server 2. > [javatest.batch] ******************************************************************************** > [javatest.batch] Completed running 9 tests. > [javatest.batch] Number of Tests Passed = 2 > [javatest.batch] Number of Tests Failed = 7 > [javatest.batch] Number of Tests with Errors = 0 > [javatest.batch] ******************************************************************************** > [javatest.batch] FAILED........com/sun/ts/tests/jsf/spec/flows/basicflowcall/URLClient.jav... > [javatest.batch] FAILED........com/sun/ts/tests/jsf/spec/flows/basicimplicit/URLClient.jav... > [javatest.batch] FAILED........com/sun/ts/tests/jsf/spec/flows/basicmethodcall/URLClient.j... > [javatest.batch] PASSED........com/sun/ts/tests/jsf/spec/flows/basicmultipage/URLClient.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jsf/spec/flows/basicmultipage/URLClient.ja... > [javatest.batch] FAILED........com/sun/ts/tests/jsf/spec/flows/basicswitch/URLClient.java#... > [javatest.batch] FAILED........com/sun/ts/tests/jsf/spec/flows/factory/URLClient.java#face... > [javatest.batch] PASSED........com/sun/ts/tests/jsf/spec/flows/intermediate/URLClient.java... > [javatest.batch] FAILED........com/sun/ts/tests/jsf/spec/flows/intermediate/URLClient.java... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5205) Use Module.findServices() to load Security Providers

by Richard Opalka (Jira)

Richard Opalka created WFCORE-5205: -------------------------------------- Summary: Use Module.findServices() to load Security Providers Key: WFCORE-5205 URL: https://issues.redhat.com/browse/WFCORE-5205 Project: WildFly Core Issue Type: Enhancement Components: Security Reporter: Richard Opalka Assignee: Richard Opalka -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 2020