[ https://issues.apache.org/jira/browse/ATLAS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705261#comment-14705261 ]
Venkatesh Seetharam edited comment on ATLAS-118 at 8/20/15 4:54 PM: -------------------------------------------------------------------- The only dependency is the client and lets disable bundling log4j with the client. This can be easily achieved with maven filter resources. was (Author: svenkat): The only dependency is the client and lets disable bundling log4j with the client. > rename atlas log4j configuration files to avoid config collisions with other > projects > ------------------------------------------------------------------------------------- > > Key: ATLAS-118 > URL: https://issues.apache.org/jira/browse/ATLAS-118 > Project: Atlas > Issue Type: Bug > Affects Versions: 0.6-incubating > Reporter: Jonathan Maron > Assignee: Jonathan Maron > Fix For: 0.6-incubating > > Original Estimate: 48h > Remaining Estimate: 48h > > There appear to be instances in which using the default name for log4j > configuration (e.g. log4j.xml) will cause the atlas version of the file to be > picked up and utilized by other projects (e.g. hive/hcat). This can actually > lead to issues with the functionality of other projects, especially if they > are dependent on log parsing. > The log4j.xml file will be renamed to atlas-log4j.xml and explicitly > referenced from the scripts via the 'log4j.configuration' system property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)