April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11316) Remove unused dependencies from org.jberet.jberet-core

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-11316?page=com.atlassian.jira.plugi... ] Yeray Borges Santana commented on WFLY-11316: --------------------------------------------- Hello [~rchakrab], feel free to take this on if you want. As usual in relation to this sort of issues, you should do a deep scanning of dependencies use and identify class loading and service loader patterns to ensure the removed dependency is no longer used. You already know they are a bit tricky, thanks ! > Remove unused dependencies from org.jberet.jberet-core > ------------------------------------------------------ > > Key: WFLY-11316 > URL: https://issues.redhat.com/browse/WFLY-11316 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Optional > > Analysis of org.jberet.jberet-core shows: > * org.jboss.jts is unused > * jberet only uses javax.enterprise.api, javax.inject.api, javax.annotation.api and javax.batch.api from javaee.api, maybe we could reduce the final size removing javaee.api and add only the required modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2466) add isTraceEnabled() when log.trace

by Baoyi Chen (Jira)

Baoyi Chen created JGRP-2466: -------------------------------- Summary: add isTraceEnabled() when log.trace Key: JGRP-2466 URL: https://issues.redhat.com/browse/JGRP-2466 Project: JGroups Issue Type: Enhancement Affects Versions: 4.2.2 Reporter: Baoyi Chen Assignee: Bela Ban Attachments: alloc.svg we use [async-profiler|https://github.com/jvm-profiling-tools/async-profiler] to profiling our project's temporary object allocation. found that jrgoups log.trace take up a certain amount of memory space. more details please refer the attachment. could we add isTraceEnabled() condition when print the trace log? that could be improve the temporary object allocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13371) Clarify the MicroProfile subsystem dependency trees

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13371?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13371: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13206 > Clarify the MicroProfile subsystem dependency trees > --------------------------------------------------- > > Key: WFLY-13371 > URL: https://issues.redhat.com/browse/WFLY-13371 > Project: WildFly > Issue Type: Task > Components: Build System, MP Config, MP Fault Tolerance, MP Health, MP JWT, MP Metrics, MP OpenAPI, MP OpenTracing > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 20.0.0.Beta1 > > > The MP specs evolve at a different pace from the EE specs that make up the bulk of WildFly, so I want to maintain as much flexibility as possible in terms of how we package and distribute them. A small step in that direction is just being clear about the dependency trees for the various maven modules we use to provide these specs. IOWs, don't allow non-test-scope transitive dependencies to come through any dependencies on the artifacts coming from the WF build itself or from WF Core. Add global exclusions to any direct dependencies on those and add explicit dependencies for anything that was coming in transitively, > Doing this would be good across the WF code base but here the focus is the MP maven modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12510) Update usages of wildfly-credential-reference_1_0.xsd to the new wildfly-credential-reference_1_1.xsd for new schemas

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-12510?page=com.atlassian.jira.plugi... ] Farah Juma commented on WFLY-12510: ----------------------------------- [~jmesnil] My WildFly PR for EAP7-676 does revert the temporary schema updates that were made for WFLY-12510 and bumps the various schemas to new versions and updates these new versions to the 1.1 version of the credential-reference schema: https://github.com/wildfly/wildfly/pull/12538 > Update usages of wildfly-credential-reference_1_0.xsd to the new wildfly-credential-reference_1_1.xsd for new schemas > --------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12510 > URL: https://issues.redhat.com/browse/WFLY-12510 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Farah Juma > Assignee: Jeff Mesnil > Priority: Major > > With WFCORE-4150, the WildFly Core's urn:jboss:domain:13.0 namespace now references wildfly-credential-reference_1_1.xsd. > WildFly full tests that any schemas that we shipped is up to date with the latest urn:jboss:domain:13.0 namespace in StandardConfigsXMLValidationUnitTestCase tests. > However when this test resolves urn:jboss:domain:13.0, it also resolve urn:wildfly:credential-reference:1.1 and then the test fails because subsystems schemas that references urn:wildfly:credential-reference:1.0 are incorrectly considered not updated. > Released schemas must not be updated with urn:wildfly:credential-reference:1.1 as they are already out in the open. > However every new schemas that will be released with WildFly 20 must ensure that they will updated their references from urn:wildfly:credential-reference:1.0 to urn:wildfly:credential-reference:1.1. > I'll create separate WFLY issues for each involved component as they may update their schemas at different time during the development of WildFly 20. > There is no need to update the schema just for this reference change but if the schema is updated for another reason, then the reference to urn:wildfly:credential-reference MUST be updated -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13372) Add JAXRS.adoc reference to Subsystem_configuration.adoc in Admin Guide

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-13372?page=com.atlassian.jira.plugi... ] Ronald Sigal commented on WFLY-13372: ------------------------------------- [~kabirkhan], FYI. > Add JAXRS.adoc reference to Subsystem_configuration.adoc in Admin Guide > ----------------------------------------------------------------------- > > Key: WFLY-13372 > URL: https://issues.redhat.com/browse/WFLY-13372 > Project: WildFly > Issue Type: Task > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > > Now that the jaxrs subsystem has the ability to change RESTEasy parameters, I wrote docs/src/main/asciidoc/_admin-guide/subsystem-configuration/JAXRS.adoc, but I forgot to include it in Chapter 9. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13372) Add JAXRS.adoc reference to Subsystem_configuration.adoc in Admin Guide

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-13372?page=com.atlassian.jira.plugi... ] Ronald Sigal reassigned WFLY-13372: ----------------------------------- Assignee: Ronald Sigal (was: Brian Stansberry) > Add JAXRS.adoc reference to Subsystem_configuration.adoc in Admin Guide > ----------------------------------------------------------------------- > > Key: WFLY-13372 > URL: https://issues.redhat.com/browse/WFLY-13372 > Project: WildFly > Issue Type: Task > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > > Now that the jaxrs subsystem has the ability to change RESTEasy parameters, I wrote docs/src/main/asciidoc/_admin-guide/subsystem-configuration/JAXRS.adoc, but I forgot to include it in Chapter 9. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13372) Add JAXRS.adoc reference to Subsystem_configuration.adoc in Admin Guide

by Ronald Sigal (Jira)

Ronald Sigal created WFLY-13372: ----------------------------------- Summary: Add JAXRS.adoc reference to Subsystem_configuration.adoc in Admin Guide Key: WFLY-13372 URL: https://issues.redhat.com/browse/WFLY-13372 Project: WildFly Issue Type: Task Reporter: Ronald Sigal Assignee: Brian Stansberry Now that the jaxrs subsystem has the ability to change RESTEasy parameters, I wrote docs/src/main/asciidoc/_admin-guide/subsystem-configuration/JAXRS.adoc, but I forgot to include it in Chapter 9. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13371) Clarify the MicroProfile subsystem dependency trees

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13371: --------------------------------------- Summary: Clarify the MicroProfile subsystem dependency trees Key: WFLY-13371 URL: https://issues.redhat.com/browse/WFLY-13371 Project: WildFly Issue Type: Task Components: Build System, MP Config, MP Fault Tolerance, MP Health, MP JWT, MP Metrics, MP OpenAPI, MP OpenTracing Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 20.0.0.Beta1 The MP specs evolve at a different pace from the EE specs that make up the bulk of WildFly, so I want to maintain as much flexibility as possible in terms of how we package and distribute them. A small step in that direction is just being clear about the dependency trees for the various maven modules we use to provide these specs. IOWs, don't allow non-test-scope transitive dependencies to come through any dependencies on the artifacts coming from the WF build itself or from WF Core. Add global exclusions to any direct dependencies on those and add explicit dependencies for anything that was coming in transitively, Doing this would be good across the WF code base but here the focus is the MP maven modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13370) Eliminate fault-tolerance/executor dependence on ee subsystem module

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13370: --------------------------------------- Summary: Eliminate fault-tolerance/executor dependence on ee subsystem module Key: WFLY-13370 URL: https://issues.redhat.com/browse/WFLY-13370 Project: WildFly Issue Type: Task Components: MP Fault Tolerance Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 20.0.0.Beta1 FaultToleranceContainerExecutorFactory has a compile time dep on the ee subsystem module just so it can cast the ThreadFactory it looks up in JNDI to org.jboss.as.ee.concurrent.ManagedThreadFactoryImpl before returning it as a plain old ThreadFactory. We should avoid deps between extensions. For this one, if the cast is necessary at all (i.e. as a check that the JNDI lookup is producing something valid), a cast to javax.enterprise.concurrent.ManagedThreadFactory should suffice. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5204) Replace DMN Validator with generic validator for subsumption and redundancy

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5204?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-5204: ------------------------------------ Assignee: Toni Rikkola (was: Mario Fusco) > Replace DMN Validator with generic validator for subsumption and redundancy > --------------------------------------------------------------------------- > > Key: DROOLS-5204 > URL: https://issues.redhat.com/browse/DROOLS-5204 > Project: Drools > Issue Type: Task > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 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 April 2020