You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Tomohito Nakayama (JIRA)" <de...@db.apache.org> on 2005/09/01 12:45:36 UTC
[jira] Updated: (DERBY-549) remove Diagnostic framework from Derby
[ http://issues.apache.org/jira/browse/DERBY-549?page=all ]
Tomohito Nakayama updated DERBY-549:
------------------------------------
Description:
There are question wheter Diagnostic framework should exists in derby, because the functionality it is trying to provide is really the domain of Java debugger.
This issue was invoked by next mail posted by Dan.
http://permalink.gmane.org/gmane.comp.apache.db.derby.devel/7737
was:
There are question wheter Diagnostic framework should be exists in derby, because the functionality it is trying to provide is really the domain ofa Java debugger.
This issue was invoked by next mail posted by Dan.
http://permalink.gmane.org/gmane.comp.apache.db.derby.devel/7737
> remove Diagnostic framework from Derby
> --------------------------------------
>
> Key: DERBY-549
> URL: http://issues.apache.org/jira/browse/DERBY-549
> Project: Derby
> Type: Task
> Components: Services
> Reporter: Tomohito Nakayama
>
> There are question wheter Diagnostic framework should exists in derby, because the functionality it is trying to provide is really the domain of Java debugger.
> This issue was invoked by next mail posted by Dan.
> http://permalink.gmane.org/gmane.comp.apache.db.derby.devel/7737
--
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