[JBoss JIRA] (LOGTOOL-144) Make JBoss logging annotations accessible at runtime
by Francois JACQUES (Jira)
Francois JACQUES created LOGTOOL-144:
----------------------------------------
Summary: Make JBoss logging annotations accessible at runtime
Key: LOGTOOL-144
URL: https://issues.redhat.com/browse/LOGTOOL-144
Project: Log Tool
Issue Type: Enhancement
Reporter: Francois JACQUES
Hi,
We have a use case where we are creating a Java proxy to access meta information of a logger. In this scenario we need to access the `@Message` and `@MessageLogger` annotations at runtime. This is not possible as there retention policy is set to `@Retention(CLASS)`.
Do you see any problem/value into changing the retention policy to runtime for all annotations in JBoss logging ?
Thanks
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months
[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ]
Lin Gao reassigned WFLY-12913:
------------------------------
Assignee: Lin Gao
> Rationalize com.sum.xml.bind module dependencies
> ------------------------------------------------
>
> Key: WFLY-12913
> URL: https://issues.redhat.com/browse/WFLY-12913
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate, REST, Web Services
> Reporter: Brian Stansberry
> Assignee: Lin Gao
> Priority: Minor
>
> The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents:
> {code}
> <module name="com.github.relaxng" export="true" />
> <module name="com.sun.istack" export="true" />
> <module name="com.sun.xml.txw2" export="true" />
> <module name="com.sun.xsom" export="true" />
> {code}
> Task is to:
> 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules.
> 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules.
> 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months
[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ]
Lin Gao commented on WFLY-12913:
--------------------------------
Refer to: https://github.com/wildfly/wildfly/pull/12856 for the context about this issue.
> Rationalize com.sum.xml.bind module dependencies
> ------------------------------------------------
>
> Key: WFLY-12913
> URL: https://issues.redhat.com/browse/WFLY-12913
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate, REST, Web Services
> Reporter: Brian Stansberry
> Priority: Minor
>
> The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents:
> {code}
> <module name="com.github.relaxng" export="true" />
> <module name="com.sun.istack" export="true" />
> <module name="com.sun.xml.txw2" export="true" />
> <module name="com.sun.xsom" export="true" />
> {code}
> Task is to:
> 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules.
> 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules.
> 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months
[JBoss JIRA] (JGRP-2427) UDP: change methods deprecated in Java 14
by Bela Ban (Jira)
Bela Ban created JGRP-2427:
------------------------------
Summary: UDP: change methods deprecated in Java 14
Key: JGRP-2427
URL: https://issues.redhat.com/browse/JGRP-2427
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 5.0
Several methods in UDP will get deprecated in Java 14, e.g. {{MulticastSocket.joinGroup()/leaveGroup()/setInterface()}} etc.
They can be replaced with their suggested alternatives, even in Java 11 (these methods are already present).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months