You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by ji...@apache.org on 2004/09/21 16:59:37 UTC

[jira] Created: (DIRSEDA-11) Remove dependency on commons-logging

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSEDA-11

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSEDA-11
    Summary: Remove dependency on commons-logging
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Seda Framework

   Assignee: 
   Reporter: Alex Karasulu

    Created: Tue, 21 Sep 2004 7:59 AM
    Updated: Tue, 21 Sep 2004 7:59 AM

Description:
There are a bunch of LoggingXxxxxMonitor implementations that log monitor events using commons-logging.  These classes are NOT used in any of the POJO's but as monitors they can be set on the POJOs to log events.  

A Java application serving as a harness for protocol developers using our SEDA framework will use these logging monitors.  The trivial usage of logging here in printing to the stderr is something that we could easily implement without introducing the CL dependency which is a concern in the community.  Here's an email trail where there were discussions on this topic.  The final conclusion was to just implement a simple console logger rather than have the CL dependency.

So what needs to be done is the removal of all CL deps in all monitors.  Plus when using the commons-threadpool we need to implement our own logging monitor rather than using the one for CL.

Good luck,
Alex



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[jira] Closed: (DIRSEDA-11) Remove dependency on commons-logging

Posted by ji...@apache.org.
Message:

   The following issue has been closed.

   Resolver: Alex Karasulu
       Date: Tue, 21 Sep 2004 2:13 PM

There still seems to be controversy around this so I'll leave it as is for now.  See the following thread for more details:

http://nagoya.apache.org/eyebrowse/BrowseList?listName=directory-dev@incubator.apache.org&by=thread&from=883330


---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DIRSEDA-11

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DIRSEDA-11
    Summary: Remove dependency on commons-logging
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: WON'T FIX

    Project: Seda Framework

   Assignee: 
   Reporter: Alex Karasulu

    Created: Tue, 21 Sep 2004 7:59 AM
    Updated: Tue, 21 Sep 2004 2:13 PM

Description:
There are a bunch of LoggingXxxxxMonitor implementations that log monitor events using commons-logging.  These classes are NOT used in any of the POJO's but as monitors they can be set on the POJOs to log events.  

A Java application serving as a harness for protocol developers using our SEDA framework will use these logging monitors.  The trivial usage of logging here in printing to the stderr is something that we could easily implement without introducing the CL dependency which is a concern in the community.  Here's an email trail where there were discussions on this topic.  The final conclusion was to just implement a simple console logger rather than have the CL dependency.

So what needs to be done is the removal of all CL deps in all monitors.  Plus when using the commons-threadpool we need to implement our own logging monitor rather than using the one for CL.

Good luck,
Alex



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira