[ http://issues.apache.org/jira/browse/BEEHIVE-627?page=all ]
Eddie O'Neil updated BEEHIVE-627:
---------------------------------
Assign To: Eddie O'Neil
Yeah, I agree with you. Logging should be something that the user can *enable*
not something that must be disabled.
Once the system control builds are all wired up, I'll remove the log4j.* config
files from the control JARs.
> Beehive controls should not provide log4j config files
> ------------------------------------------------------
>
> Key: BEEHIVE-627
> URL: http://issues.apache.org/jira/browse/BEEHIVE-627
> Project: Beehive
> Type: Bug
> Components: Controls
> Versions: V1
> Reporter: Jim Cummings
> Assignee: Eddie O'Neil
> Fix For: V1
>
> Beehive control jars should not provide log4j.* config files in their jars.
> This can have unexpected behavior for clients if log4j picks up these
> unintended config files.
> I believe the webservice control is the only one that does this, but I'm not
> certain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
