Bug 116814 - Command line tools run with 'ccm-run' don't pick up log4j config
Summary: Command line tools run with 'ccm-run' don't pick up log4j config
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: installation
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dennis Gregorovic
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks: 113496
TreeView+ depends on / blocked
 
Reported: 2004-02-25 14:20 UTC by Daniel Berrangé
Modified: 2007-04-18 17:03 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-03-01 16:21:11 UTC
Embargoed:

Attachments (Terms of Use)

Description Daniel Berrangé 2004-02-25 14:20:25 UTC 
Description of problem:
If i make changes to /etc/ccm/conf/log4j.properties, these are not
picked up when running command line tools with 'ccm-run'. A workaround
is to add /etc/ccm/conf to /etc/ccm/ccm.classpath, but there must be a
better way.

Version-Release number of selected component (if applicable):


How reproducible:
ALWAYS

Steps to Reproduce:
1. Change log level for some class
2. Run ccm-run <tool>
3.
  
Actual results:
No logs are output

Expected results:
Logs are output

Additional info:
Comment 1 Dennis Gregorovic 2004-03-01 16:21:11 UTC 
@ 40915
Note You need to log in before you can comment on or make changes to this bug.