[
https://jira.jboss.org/jira/browse/ISPN-162?page=com.atlassian.jira.plugi...
]
Galder Zamarreno commented on ISPN-162:
---------------------------------------
Sorry Manik, got confused with the initial statement you made. Thought you're
suggesting that the log4j.xml was included in the infinispan-core.jar and to that I was
saying no way of doing that and keeping the name as log4j.xml. For the distro yeah,
it's fine to keep it as log4j.xml cos if it's included or not in the classpath is
a matter of changing the classpath and removing /etc from it. However, if the log4j.xml
had been included with that name in the core jar, that would be a problem.
Hence, this can be marked as resolved now. No more work needs to be done.
Add excludes for log4j.xml to test jar generation
-------------------------------------------------
Key: ISPN-162
URL:
https://jira.jboss.org/jira/browse/ISPN-162
Project: Infinispan
Issue Type: Task
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 4.0.0.BETA1
While working on the ISPN cache provider, I've realised that the test
jar contains a log4j.xml and this stops you from using a different log4j
settings to the one in the test jar. This is because log4j first and
foremost looks for a 'log4j.xml' and if present, it uses that. This
cannot be overriden with -Dlog4j.configuration.
As a result, I'm adding an excludes to avoid this log4j.xml ending up in
the test jar. The other alternative would be to rename
src/test/resources/log4j.xml to something else, i.e.
log4j-infinispan.xml but doing this would stop the log4j settings from
being picked up by default during Infinispan development, hence, I think
the excludes setting is the best option here.
If anyone has any issues with this, let me know.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira