db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-569) Derby network server is printing connection activity on System.out instead of logging it to derby.log
Date Tue, 08 Nov 2005 00:15:20 GMT
    [ http://issues.apache.org/jira/browse/DERBY-569?page=comments#action_12356995 ] 

Kathey Marsden commented on DERBY-569:
--------------------------------------

OK I will check in as soon as ...
1)  I hear from you that the ICLA is in the mail
2) We have one more binding +1 for the change.
3)  The vote has been up for 24 hours to allow anyone to object.  11/8/2005 1:30pm PST . (Normally
I would let it sit for a week but this doesn't seem very controversial.)
    

Thank you for  following through so completely on this change and making the doc changes.
   For the release notes I guess the correct  thing to do for now is put this in the CHANGES
file. I noticed  that the CHANGES  file in the trunk has not been restarted  for 10.2. It
would be ok to  just start over with "Changes in Derby 10.2" and put your  change in that
text file.    The release page happen at the time of the release and this note in the CHANGES
file will get picked up then I think.

> Derby network server is printing connection activity on System.out instead of logging
it to derby.log
> -----------------------------------------------------------------------------------------------------
>
>          Key: DERBY-569
>          URL: http://issues.apache.org/jira/browse/DERBY-569
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>     Versions: 10.0.2.1
>  Environment: solaris (but it may not be relevant)
>     Reporter: Xavier-Francois VIGOUROUX
>     Priority: Trivial
>  Attachments: svn2.diff
>
> All the messages are going to the derby.log file except the connection activity. For
me,tThis information is not
> important enough to be logged to console.

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