[ https://issues.jboss.org/browse/WFLY-12282?page=com.atlassian.jira.plugin... ]
Eduardo Martins updated WFLY-12282:
-----------------------------------
Description:
This kind of thing is a bug:
https://github.com/wildfly/wildfly/blob/8d46601ce6757d26877df6cb61d56a90a...
The subsystem exposes a capability so consumers of its services should use the capabilities API to handle requiring it and accessing its services.
was:
This kind of thing is a bug:
https://github.com/wildfly/wildfly/blob/master/ee/src/main/java/org/jboss...
The subsystem exposes a capability so consumers of its services should use the capabilities API to handle requiring it and accessing its services.
There's probably missing capability wiring within the concurrency resources as well; e.g. for dependency by executors on thread factories.
> Batch resources should use request-controller capability wiring
> ---------------------------------------------------------------
>
> Key: WFLY-12282
> URL: https://issues.jboss.org/browse/WFLY-12282
> Project: WildFly
> Issue Type: Bug
> Components: Concurrency Utilities
> Affects Versions: 16.0.0.Final
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Major
>
> This kind of thing is a bug:
> https://github.com/wildfly/wildfly/blob/8d46601ce6757d26877df6cb61d56a90a...
> The subsystem exposes a capability so consumers of its services should use the capabilities API to handle requiring it and accessing its services.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[ https://issues.jboss.org/browse/WFLY-12282?page=com.atlassian.jira.plugin... ]
Eduardo Martins updated WFLY-12282:
-----------------------------------
Component/s: Batch
(was: Concurrency Utilities)
> Batch resources should use request-controller capability wiring
> ---------------------------------------------------------------
>
> Key: WFLY-12282
> URL: https://issues.jboss.org/browse/WFLY-12282
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Affects Versions: 16.0.0.Final
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Major
>
> This kind of thing is a bug:
> https://github.com/wildfly/wildfly/blob/8d46601ce6757d26877df6cb61d56a90a...
> The subsystem exposes a capability so consumers of its services should use the capabilities API to handle requiring it and accessing its services.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
Eduardo Martins created WFLY-12282:
--------------------------------------
Summary: Batch resources should use request-controller capability wiring
Key: WFLY-12282
URL: https://issues.jboss.org/browse/WFLY-12282
Project: WildFly
Issue Type: Bug
Components: Concurrency Utilities
Affects Versions: 16.0.0.Final
Reporter: Eduardo Martins
Assignee: Eduardo Martins
This kind of thing is a bug:
https://github.com/wildfly/wildfly/blob/master/ee/src/main/java/org/jboss...
The subsystem exposes a capability so consumers of its services should use the capabilities API to handle requiring it and accessing its services.
There's probably missing capability wiring within the concurrency resources as well; e.g. for dependency by executors on thread factories.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[ https://issues.jboss.org/browse/DROOLS-4192?page=com.atlassian.jira.plugi... ]
Jiri Petrlik updated DROOLS-4192:
---------------------------------
Story Points: 3
> Check whether there's a logback file breaking logging
> -----------------------------------------------------
>
> Key: DROOLS-4192
> URL: https://issues.jboss.org/browse/DROOLS-4192
> Project: Drools
> Issue Type: Enhancement
> Reporter: Luca Molteni
> Assignee: Jiri Petrlik
> Priority: Minor
>
> When there's a logback file in src/main/resources every project that use that module has the logging broken.
> We should create an enforcer rule that checks whether there are no logback files in src/main/resources
> With this commit
> https://github.com/kiegroup/drools/commit/82358d515a5afe079b7aebe9f3afcfa...
> we fixed logging.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)