January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1919) Release WildFly Elytron 1.11.0.Final

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1919?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELY-1919. ----------------------------- Resolution: Done > Release WildFly Elytron 1.11.0.Final > ------------------------------------ > > Key: ELY-1919 > URL: https://issues.redhat.com/browse/ELY-1919 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.11.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4796) Upgrade Elytron Web to 1.7.0.Final

by Farah Juma (Jira)

Farah Juma created WFCORE-4796: ---------------------------------- Summary: Upgrade Elytron Web to 1.7.0.Final Key: WFCORE-4796 URL: https://issues.redhat.com/browse/WFCORE-4796 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-87) Release Elytron Web 1.7.0.Final

by Farah Juma (Jira)

Farah Juma created ELYWEB-87: -------------------------------- Summary: Release Elytron Web 1.7.0.Final Key: ELYWEB-87 URL: https://issues.redhat.com/browse/ELYWEB-87 Project: Elytron Web Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma Fix For: 1.7.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-88) Upgrade WildFly Elytron to 1.11.0.Final

by Farah Juma (Jira)

Farah Juma created ELYWEB-88: -------------------------------- Summary: Upgrade WildFly Elytron to 1.11.0.Final Key: ELYWEB-88 URL: https://issues.redhat.com/browse/ELYWEB-88 Project: Elytron Web Issue Type: Component Upgrade Reporter: Farah Juma Assignee: Farah Juma Fix For: 1.7.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1919) Release WildFly Elytron 1.11.0.Final

by Farah Juma (Jira)

Farah Juma created ELY-1919: ------------------------------- Summary: Release WildFly Elytron 1.11.0.Final Key: ELY-1919 URL: https://issues.redhat.com/browse/ELY-1919 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma Fix For: 1.11.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4911) Allow bound variables to be a function of 3 and 4 other variables

by Lukáš Petrovický (Jira)

Lukáš Petrovický created DROOLS-4911: ---------------------------------------- Summary: Allow bound variables to be a function of 3 and 4 other variables Key: DROOLS-4911 URL: https://issues.redhat.com/browse/DROOLS-4911 Project: Drools Issue Type: Enhancement Components: executable model Affects Versions: 7.31.0.Final Reporter: Lukáš Petrovický Assignee: Lukáš Petrovický Fix For: 7.32.0.Final For a use case in OptaPlanner's Constraint Streams (see PLANNER-1764), I need to be able to call variable binding functions with 3 or 4 arguments. This will allow me to handle cases like this: {noformat} $p1: Person() $p2: Person() $p3: Person($allMoney: $p1.money + $p2.money + $p3.money) {noformat} At the moment, Drools exec model only supports cases of up to 2 arguments. I need to bring the number up to 4. I do not plan to introduce this functionality into DRL, as my use case leverages exec model directly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12941) , Count metrics in wildfly17 does not increase

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12941?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-12941: ----------------------------------------- [~alireza.alallah] Can you be more specific? There are many different subsystems in WildFly that provide their own metrics so knowing which are a problem will help. Also, many subsystems have a 'statistics-enabled' configuration attribute with a default value of 'false'. (It's false by default because collection metrics has a perf impact so we want users to opt into it.) If that attribute is 'false' for a subsystem it may look like some metrics don't move from 0. > ,Count metrics in wildfly17 does not increase > --------------------------------------------- > > Key: WFLY-12941 > URL: https://issues.redhat.com/browse/WFLY-12941 > Project: WildFly > Issue Type: Bug > Reporter: alireza alallah > Assignee: Brian Stansberry > Priority: Major > > Count metrics in wildfly17 does not increase -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1084) kjar maven dependencies are downloaded even if scope is set to provided or test

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-1084?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-1084. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/70e5b2be5db1b610db41e2cecc9b0ea... > kjar maven dependencies are downloaded even if scope is set to provided or test > ------------------------------------------------------------------------------- > > Key: DROOLS-1084 > URL: https://issues.redhat.com/browse/DROOLS-1084 > Project: Drools > Issue Type: Bug > Affects Versions: 6.3.0.Final > Reporter: Lindsay Thurmond > Assignee: Mario Fusco > Priority: Major > Attachments: debug1.png, debug2.png, debug3.png > > > The creation of a new kbase triggers the specified rules kjar to be downloaded from the remote Maven repository. This works as expected but has the side effect of also downloading the Maven dependencies for the kjar. The problem is that it is downloading ALL the Maven dependencies even if they are specified as provided or test scope. This shouldn't happen since provided dependencies are expected to already be on the classpath and we should never need test dependencies at all during runtime at all. > I did some digging into the Drools source to and found out that > {{KieRepositoryImpl#getKieModule()}} > contains logic to check the classpath for the KieModule and if it can't find it to load everything from the Maven repo which includes downloading all the dependencies (and dependencies of dependencies and so on). > Unfortunately the code for checking the classpath is not actually implemented and looks like this: > {code} > private KieModule checkClasspathForKieModule(ReleaseId releaseId) { > // TODO > // ClassLoader classLoader = Thread.currentThread().getContextClassLoader(); > // URL url = classLoader.getResource( ((ReleaseIdImpl)releaseId).getPomPropertiesPath() ); > return null; > } > {code} > After nothing is found on the classpath everything is downloaded from Maven. You can see all the stuff that is going to be downloaded (if it's not already in your Maven repo) in > {{DefaultProjectDependenciesResolver#resolve() //line 159}} > You can even see here that the dependencies have been marked as provided, but regardless they are going to be downloaded. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4793) Upgrade WildFly Elytron to 1.11.0.CR5

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-4793?page=com.atlassian.jira.plug... ] Farah Juma updated WFCORE-4793: ------------------------------- Fix Version/s: 11.0.0.Beta6 (was: 11.0.0.Beta7) > Upgrade WildFly Elytron to 1.11.0.CR5 > ------------------------------------- > > Key: WFCORE-4793 > URL: https://issues.redhat.com/browse/WFCORE-4793 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 11.0.0.Beta6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4794) Upgrade Elytron Web to 1.7.0.CR4

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-4794?page=com.atlassian.jira.plug... ] Farah Juma updated WFCORE-4794: ------------------------------- Fix Version/s: 11.0.0.Beta6 (was: 11.0.0.Beta7) > Upgrade Elytron Web to 1.7.0.CR4 > -------------------------------- > > Key: WFCORE-4794 > URL: https://issues.redhat.com/browse/WFCORE-4794 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 11.0.0.Beta6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 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 January 2020