Bug 778323 (SOA-808) - Embedded all, default and minimal deploys still have verbose logging
Summary: Embedded all, default and minimal deploys still have verbose logging
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-808
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process, Embedded Server, Monitoring and Management
Version: 4.3 IR4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 IR5
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-18 15:34 UTC by Julian Coleman
Modified: 2008-12-16 14:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-07 09:13:34 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-808 0 None None None Never

Description Julian Coleman 2008-09-18 15:34:52 UTC 
Complexity: Low
Date of First Response: 2008-10-07 05:13:34
project_key: SOA

The fix for SOA-536 doesn't alter the jboss-log4j.xml files in the all, default and minimal deploys.
This is not sensible.
Comment 1 Julian Coleman 2008-09-19 11:33:03 UTC 
Fixed in revision 1954 of
  build-tools/builders/eap/build.xml

Commit message:

  Cut down the logging verbosity for hibernate and jBPM in the all, default and
  minimal deploys - as is done for the standalone (default) deploy.
  (This removes a difference between the embedded and standalone versions.
  Fixes JIRA SOA-808.
Comment 2 Jiri Pechanec 2008-10-07 09:13:34 UTC 
Verified in IR5
Comment 3 Julian Coleman 2008-12-16 14:12:32 UTC 
Changes also added to 4.2.0 branch in revision 2464 of:
  builders/eap/build.xml
  builders/esb/build.xml
  resource/conf-skeleton/jboss-log4j.xml (deleted)
  resource/conf-skeleton/jboss-log4j-default.xml (added)
  resource/conf-skeleton/jboss-log4j-production.xml (added)
(this will be in the next CR build of 4.2.0 CP03).
Note You need to log in before you can comment on or make changes to this bug.