[jboss-jira] [JBoss JIRA] (JGRP-1962) Do not include the log4j2.xml resource in the released JGroups jar

[Sanne Grinovero (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107418#comment-13107418 ] 

Sanne Grinovero commented on JGRP-1962:
---------------------------------------

You can keep it in your project among the tests, but it doesn't have to be included in the released jar.
(On top of that, I'm not sure it's useful to include the README and all other resources: I think the fatten the jar without much benefit)

People can use the property you suggest, but unless I know that you're bundling the file (and even using the default resource name! ) I will assume that it's enough to add a {{log4j2.xml}} to my classpath and be set. It was painful debugging to figure out why it wasn't being effective.

> Do not include the log4j2.xml resource in the released JGroups jar
> ------------------------------------------------------------------
>
>                 Key: JGRP-1962
>                 URL: https://issues.jboss.org/browse/JGRP-1962
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 3.6.4
>            Reporter: Sanne Grinovero
>            Assignee: Bela Ban
>             Fix For: 3.6.6
>
>
> The {{log4j2.xml}} configuration file is included in JGroups, but this makes it hard to override the logging as this will likely conflict with other resources configured by end user applications.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)