[JBoss JIRA] (WFLY-13512) Duplicated classes in META-INF folder
by Antonio Fernandez Alhambra (Jira)
[ https://issues.redhat.com/browse/WFLY-13512?page=com.atlassian.jira.plugi... ]
Antonio Fernandez Alhambra moved WFCOM-61 to WFLY-13512:
--------------------------------------------------------
Project: WildFly (was: WildFly Common)
Key: WFLY-13512 (was: WFCOM-61)
Affects Version/s: (was: 1.4.0.Final)
(was: 1.5.1.Final)
> Duplicated classes in META-INF folder
> -------------------------------------
>
> Key: WFLY-13512
> URL: https://issues.redhat.com/browse/WFLY-13512
> Project: WildFly
> Issue Type: Quality Risk
> Reporter: Antonio Fernandez Alhambra
> Priority: Major
> Labels: reported-by-qe
> Attachments: Screenshot from 2020-05-14 17-20-16.png
>
>
> There are duplicated classes inside the org.wildfly.common:wildfly-common file.
> So whenever the enforcer maven plugin is used for building, if there is a dependency in the pom.xml, enforcer plugin will fail complaining about this jar due to these duplicated jar files.
> {noformat}
> Duplicate classes found:
> Found in:
> org.kie.server:kie-server-router-proxy:jar:7.38.0-SNAPSHOT:compile
> org.wildfly.common:wildfly-common:jar:1.5.1.Final:compile
> Duplicate classes:
> META-INF/versions/9/org/wildfly/common/lock/JDKSpecific.class
> META-INF/versions/9/org/wildfly/common/os/ProcessRedirect.class
> META-INF/versions/9/org/wildfly/common/lock/Substitutions$Target_PauseNode.class
> META-INF/versions/9/org/wildfly/common/os/GetProcessInfoAction.class
> META-INF/versions/9/org/wildfly/common/lock/JDKSpecific$1.class
> META-INF/versions/9/org/wildfly/common/lock/Substitutions.class
> META-INF/versions/9/org/wildfly/common/lock/Substitutions$Target_JDKSpecific.class
> META-INF/versions/11/org/wildfly/common/archive/JDKSpecific.class
> META-INF/versions/9/org/wildfly/common/cpu/ProcessorInfo.class
> {noformat}
> Seems these duplicated classes are bundled in the jar since version 1.4.x onwards.
> These duplicated classes are located in the META-INF/versions folders inside the jar.
> Attached a screenshot of the same.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5372) Investigate abstraction/coexistence
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-5372:
----------------------------------------
Summary: Investigate abstraction/coexistence
Key: DROOLS-5372
URL: https://issues.redhat.com/browse/DROOLS-5372
Project: Drools
Issue Type: Task
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
New and old PMML implementations hould live together for some time.
USer should be able to choose implementation
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5371) if (!A) { } does not compile
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5371?page=com.atlassian.jira.plug... ]
Luca Molteni moved RHDM-1362 to DROOLS-5371:
--------------------------------------------
Project: Drools (was: Red Hat Decision Manager)
Key: DROOLS-5371 (was: RHDM-1362)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: executable model
(was: BRE)
Affects Version/s: 7.37.0.Final
(was: 7.7.0.GA)
QE Status: NEW
> if (!A) { } does not compile
> ----------------------------
>
> Key: DROOLS-5371
> URL: https://issues.redhat.com/browse/DROOLS-5371
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.37.0.Final
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> A rule of the form
> if (!A) {
> f1()
> } else {
> f2()
> }
> does not compile whereas a rule of the form
> if (A) {
> f2()
> } else {
> f1()
> }
> does
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5342) Default value of "drools.lambda.introspector.cache.size" for externalized lambda
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5342?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5342:
-----------------------------------
Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 19-21 (from May 4))
> Default value of "drools.lambda.introspector.cache.size" for externalized lambda
> --------------------------------------------------------------------------------
>
> Key: DROOLS-5342
> URL: https://issues.redhat.com/browse/DROOLS-5342
> Project: Drools
> Issue Type: Task
> Components: executable model
> Affects Versions: 7.37.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Regarding the cache size default value of LambdaIntrospector.methodFingerprintsMap,
> If "drools.externaliseCanonicalModelLambda" option is not enabled, the cache is frequently used so it will not likely retain old classloaders. So the default value '32' would be fine.
> If "drools.externaliseCanonicalModelLambda" option is enabled, the cache is used in rare occasions:
> A) Lambda for binding variable (DROOLS-5328)
> B) Lambda which ExecModelLambdaPostProcessor failed to externalize (DROOLS-5329)
> So one build may use only a few entries in a cache Map. Then, the cache eventually may retain several old classloaders after multiple builds. Generally, the classloader leak issue is prioritized over build time performance benefit so '0' is the good default value when externaliseCanonicalModelLambda is enabled.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month