beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie O'Neil (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Closed: (BEEHIVE-627) Beehive controls should not provide log4j config files
Date Wed, 17 Aug 2005 22:33:54 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-627?page=all ]
     
Eddie O'Neil closed BEEHIVE-627:
--------------------------------


Looked through these and didn't see a log4j config file in the control JARs.  Closing.

> 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: v1m1
>     Reporter: Jim Cummings
>     Assignee: Zach Smith
>      Fix For: v1m1

>
> 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


Mime
View raw message