[ http://issues.apache.org/jira/browse/DERBY-1272?page=comments#action_12419810 ]
Andrew McIntyre commented on DERBY-1272: ---------------------------------------- I've svn up'd and now I'm seeing this problem too, with the build failing in iapi/types/build.xml with the patch applied. This may have uncovered a potential problem, in that something in iapi/types eventually has a dependency on BaseMonitor, which lives in impl. I'm not sure whether or not this is a serious problem, but I thought the iapi classes were not supposed to have dependencies on classes in impl. > Change sysinfo to print to error log (derby.log) on boot of derby if > derby.stream.error.logSeverityLevel=0 > ----------------------------------------------------------------------------------------------------------- > > Key: DERBY-1272 > URL: http://issues.apache.org/jira/browse/DERBY-1272 > Project: Derby > Type: Improvement > Components: Tools > Versions: 10.2.0.0, 10.1.2.1, 10.1.3.0 > Reporter: Kathey Marsden > Priority: Minor > Attachments: derby-1272-pre.diff, derby-1272-pre2.diff, derby-1272-pre3.diff > > It is often very difficult to collect correct sysinfo output from user > environments because sysinfo run from the commandline does not have the same > classpath as the jvm that started Derby or Derby was loaded with a custom > classloader. > It would be very helpful in assisting users in diagnosing their issues if > sysinfo dumped to the error log if derby.stream.error.logSeverityLevel=0 or > even by default. -- 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
