June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12177) Replace deprecated Mockito Matchers class with ArgumentMatchers

by William Collishaw (Jira)

William Collishaw created WFLY-12177: ---------------------------------------- Summary: Replace deprecated Mockito Matchers class with ArgumentMatchers Key: WFLY-12177 URL: https://issues.jboss.org/browse/WFLY-12177 Project: WildFly Issue Type: Enhancement Reporter: William Collishaw Assignee: Brian Stansberry Matchers class got replaced with ArgumentMatchers, the following is from the [Javadoc|https://static.javadoc.io/org.mockito/mockito-core/2.18.0/org/mockito/Matchers.html]: {code:java} Deprecated. Use ArgumentMatchers. This class is now deprecated in order to avoid a name clash with Hamcrest org.hamcrest.Matchers class. This class will likely be removed in version 3.0. {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10554) OpenSAML 3.3.0 complains for missing class from "metrics-core"

by Radoslav Ivanov (Jira)

[ https://issues.jboss.org/browse/WFLY-10554?page=com.atlassian.jira.plugin... ] Radoslav Ivanov edited comment on WFLY-10554 at 6/6/19 9:47 PM: ---------------------------------------------------------------- It happens during initialization of OpenSAML when calling "InitializationService::initialize" from an application startup. {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} You see, "opensaml-core" requires three services of type "org.opensaml.core.config.Initializer" (see the content of "opensaml-core-3.3.0.jar\META-INF\services\org.opensaml.core.config.Initializer"). One of them is "org.opensaml.core.metrics.impl.MetricRegistryInitializer" and it declares import of "org.opensaml.core.metrics.FilteredMetricRegistry", which uses classes from "metrics-core". was (Author: rady66): It happens during initialization of OpenSAML when calling it from an application startup. {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} You see, "opensaml-core" requires three services of type "org.opensaml.core.config.Initializer" (see the content of "opensaml-core-3.3.0.jar\META-INF\services\org.opensaml.core.config.Initializer"). One of them is "org.opensaml.core.metrics.impl.MetricRegistryInitializer" and it declares import of "org.opensaml.core.metrics.FilteredMetricRegistry", which uses classes from "metrics-core". > OpenSAML 3.3.0 complains for missing class from "metrics-core" > -------------------------------------------------------------- > > Key: WFLY-10554 > URL: https://issues.jboss.org/browse/WFLY-10554 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 13.0.0.Final > Reporter: Radoslav Ivanov > Assignee: Jim Ma > Priority: Critical > Attachments: screenshot-1.png > > > Module OpenSAML 3.3.0 requires depedency to module "io.dropwizard.metrics:metrics-core" but it does not present. As a result ClassNotFoundException is thrown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10554) OpenSAML 3.3.0 complains for missing class from "metrics-core"

by Radoslav Ivanov (Jira)

[ https://issues.jboss.org/browse/WFLY-10554?page=com.atlassian.jira.plugin... ] Radoslav Ivanov edited comment on WFLY-10554 at 6/6/19 9:36 PM: ---------------------------------------------------------------- It happens during initialization of OpenSAML when calling it from an application startup. {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} You see, "opensaml-core" requires three services of type "org.opensaml.core.config.Initializer" (see the content of "opensaml-core-3.3.0.jar\META-INF\services\org.opensaml.core.config.Initializer"). One of them is "org.opensaml.core.metrics.impl.MetricRegistryInitializer" and it declares import of "org.opensaml.core.metrics.FilteredMetricRegistry", which uses classes from "metrics-core". was (Author: rady66): It happens during initialization of OpenSAML when calling it from an application startup. {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} You see, "opensaml-core" has three services of type "org.opensaml.core.config.Initializer" - one of them is "org.opensaml.core.metrics.impl.MetricRegistryInitializer" and it is requiring "metrics-core". > OpenSAML 3.3.0 complains for missing class from "metrics-core" > -------------------------------------------------------------- > > Key: WFLY-10554 > URL: https://issues.jboss.org/browse/WFLY-10554 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 13.0.0.Final > Reporter: Radoslav Ivanov > Assignee: Jim Ma > Priority: Critical > Attachments: screenshot-1.png > > > Module OpenSAML 3.3.0 requires depedency to module "io.dropwizard.metrics:metrics-core" but it does not present. As a result ClassNotFoundException is thrown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10554) OpenSAML 3.3.0 complains for missing class from "metrics-core"

by Radoslav Ivanov (Jira)

[ https://issues.jboss.org/browse/WFLY-10554?page=com.atlassian.jira.plugin... ] Radoslav Ivanov edited comment on WFLY-10554 at 6/6/19 9:32 PM: ---------------------------------------------------------------- It happens during initialization of OpenSAML when calling it from an application startup. {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} You see, "opensaml-core" has three services of type "org.opensaml.core.config.Initializer" - one of them is "org.opensaml.core.metrics.impl.MetricRegistryInitializer" and it is requiring "metrics-core". was (Author: rady66): It happens during initialization of OpenSAML when calling it from an application. {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} You see, "opensaml-core" has three services of type "org.opensaml.core.config.Initializer" - one of them is "org.opensaml.core.metrics.impl.MetricRegistryInitializer" and it is requiring "metrics-core". > OpenSAML 3.3.0 complains for missing class from "metrics-core" > -------------------------------------------------------------- > > Key: WFLY-10554 > URL: https://issues.jboss.org/browse/WFLY-10554 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 13.0.0.Final > Reporter: Radoslav Ivanov > Assignee: Jim Ma > Priority: Critical > Attachments: screenshot-1.png > > > Module OpenSAML 3.3.0 requires depedency to module "io.dropwizard.metrics:metrics-core" but it does not present. As a result ClassNotFoundException is thrown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10554) OpenSAML 3.3.0 complains for missing class from "metrics-core"

by Radoslav Ivanov (Jira)

[ https://issues.jboss.org/browse/WFLY-10554?page=com.atlassian.jira.plugin... ] Radoslav Ivanov commented on WFLY-10554: ---------------------------------------- It happens during initialization of OpenSAML when calling it from an application. {code:java} Caused by: java.lang.NoClassDefFoundError: com/codahale/metrics/MetricRegistry at org.opensaml//org.opensaml.core.metrics.impl.MetricRegistryInitializer.init(MetricRegistryInitializer.java:42) at org.opensaml//org.opensaml.core.config.InitializationService.initialize(InitializationService.java:56) {code} You see, "opensaml-core" has three services of type "org.opensaml.core.config.Initializer" - one of them is "org.opensaml.core.metrics.impl.MetricRegistryInitializer" and it is requiring "metrics-core". > OpenSAML 3.3.0 complains for missing class from "metrics-core" > -------------------------------------------------------------- > > Key: WFLY-10554 > URL: https://issues.jboss.org/browse/WFLY-10554 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 13.0.0.Final > Reporter: Radoslav Ivanov > Assignee: Jim Ma > Priority: Critical > Attachments: screenshot-1.png > > > Module OpenSAML 3.3.0 requires depedency to module "io.dropwizard.metrics:metrics-core" but it does not present. As a result ClassNotFoundException is thrown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12176) Upgrade WildFly Core to 9.0.1.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12176?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12176: ------------------------------------ Description: Component Upgrade [WFCORE-4507] - Upgrade Jackson to 2.9.9 [WFCORE-4509] - Upgrade JBoss MSC to 1.4.7.Final Bug [WFCORE-4508] - ConcurrentModificationException in ConcreteResourceRegistration [WFCORE-4510] - remoting cannot start without default worker and does not work with non-default worker for http-upgrade was: Release Notes - WildFly Core - Version 9.0.1.Final <h2> Component Upgrade </h2> <ul> <li>[<a href='https://issues.jboss.org/browse/WFCORE-4507'>WFCORE-4507</a>] - Upgrade Jackson to 2.9.9 </li> <li>[<a href='https://issues.jboss.org/browse/WFCORE-4509'>WFCORE-4509</a>] - Upgrade JBoss MSC to 1.4.7.Final </li> </ul> <h2> Bug </h2> <ul> <li>[<a href='https://issues.jboss.org/browse/WFCORE-4508'>WFCORE-4508</a>] - ConcurrentModificationException in ConcreteResourceRegistration </li> <li>[<a href='https://issues.jboss.org/browse/WFCORE-4510'>WFCORE-4510</a>] - remoting cannot start without default worker and does not work with non-default worker for http-upgrade </li> </ul> > Upgrade WildFly Core to 9.0.1.Final > ----------------------------------- > > Key: WFLY-12176 > URL: https://issues.jboss.org/browse/WFLY-12176 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > Component Upgrade > [WFCORE-4507] - Upgrade Jackson to 2.9.9 > [WFCORE-4509] - Upgrade JBoss MSC to 1.4.7.Final > Bug > [WFCORE-4508] - ConcurrentModificationException in ConcreteResourceRegistration > [WFCORE-4510] - remoting cannot start without default worker and does not work with non-default worker for http-upgrade > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12176) Upgrade WildFly Core to 9.0.1.Final

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12176: --------------------------------------- Summary: Upgrade WildFly Core to 9.0.1.Final Key: WFLY-12176 URL: https://issues.jboss.org/browse/WFLY-12176 Project: WildFly Issue Type: Component Upgrade Reporter: Brian Stansberry Assignee: Brian Stansberry Release Notes - WildFly Core - Version 9.0.1.Final <h2> Component Upgrade </h2> <ul> <li>[<a href='https://issues.jboss.org/browse/WFCORE-4507'>WFCORE-4507</a>] - Upgrade Jackson to 2.9.9 </li> <li>[<a href='https://issues.jboss.org/browse/WFCORE-4509'>WFCORE-4509</a>] - Upgrade JBoss MSC to 1.4.7.Final </li> </ul> <h2> Bug </h2> <ul> <li>[<a href='https://issues.jboss.org/browse/WFCORE-4508'>WFCORE-4508</a>] - ConcurrentModificationException in ConcreteResourceRegistration </li> <li>[<a href='https://issues.jboss.org/browse/WFCORE-4510'>WFCORE-4510</a>] - remoting cannot start without default worker and does not work with non-default worker for http-upgrade </li> </ul> -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4509) Upgrade JBoss MSC to 1.4.7.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4509?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4509: ------------------------------------- Summary: Upgrade JBoss MSC to 1.4.7.Final (was: Release JBoss MSC to 1.4.7.Final) > Upgrade JBoss MSC to 1.4.7.Final > -------------------------------- > > Key: WFCORE-4509 > URL: https://issues.jboss.org/browse/WFCORE-4509 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 9.0.1.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4510) remoting cannot start without default worker and does not work with non-default worker for http-upgrade

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4510?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4510: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3807 > remoting cannot start without default worker and does not work with non-default worker for http-upgrade > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4510 > URL: https://issues.jboss.org/browse/WFCORE-4510 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Affects Versions: 8.0.0.Final, 9.0.0.Final > Environment: jboss-eap-7.3.0.CD16-CR1 > Reporter: Will Reichert > Assignee: Brian Stansberry > Priority: Critical > Fix For: 9.0.1.Final > > Attachments: standalone-full.noDefault.xml > > > Originally we could not get remote+http to work with a non-default worker after following all the changes we found in the schema. It looks like remoting uses the default worker even when the endpoint is configured to use a different worker. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4510) remoting cannot start without default worker and does not work with non-default worker for http-upgrade

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4510?page=com.atlassian.jira.plugi... ] Brian Stansberry moved JBEAP-17029 to WFCORE-4510: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4510 (was: JBEAP-17029) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Remoting (was: Remoting) Affects Version/s: 9.0.0.Final (was: 7.3.0.CD16) > remoting cannot start without default worker and does not work with non-default worker for http-upgrade > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4510 > URL: https://issues.jboss.org/browse/WFCORE-4510 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Affects Versions: 9.0.0.Final > Environment: jboss-eap-7.3.0.CD16-CR1 > Reporter: Will Reichert > Assignee: Flavia Rainone > Priority: Critical > Attachments: standalone-full.noDefault.xml > > > Originally we could not get remote+http to work with a non-default worker after following all the changes we found in the schema. It looks like remoting uses the default worker even when the endpoint is configured to use a different worker. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019