You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexei Zakharov (JIRA)" <ji...@apache.org> on 2007/02/09 14:18:05 UTC
[jira] Resolved: (HARMONY-3142) [classlib] [logging] Unit test for
getLoggingMXBean method implemented in HARMONY-3075
[ https://issues.apache.org/jira/browse/HARMONY-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexei Zakharov resolved HARMONY-3142.
--------------------------------------
Resolution: Fixed
Andrey, I've committed the test at the revision 505277. Please check. If the test is ok then we may close both JIRAs I think.
> [classlib] [logging] Unit test for getLoggingMXBean method implemented in HARMONY-3075
> --------------------------------------------------------------------------------------
>
> Key: HARMONY-3142
> URL: https://issues.apache.org/jira/browse/HARMONY-3142
> Project: Harmony
> Issue Type: Test
> Components: Classlib
> Reporter: Andrey Yakushev
> Assigned To: Alexei Zakharov
> Priority: Minor
> Attachments: testGetLoggingMXBean.patch
>
>
> Alexei asked me to create a patch with the unit test for getLoggingMXBean method implemented in HARMONY-3075.
> Really this method functionality is checked in tests.java.util.logging.LoggingMXBeanTest from lang-management module. (By the way should it be moved to logging module instead?)
> Nevetheless I decided suggesting additional simple check for org.apache.harmony.logging.tests.java.util.logging.LogManagerTest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.