This is a mirror bug of ISSUE #71.
Filed here for the tracking pusposes while jtharness java.net migration is being settled.

This issue was originally targeted for 4.3, but it was not fixed in that
release, so could you please consider it for 4.4 version (it is not listed in 4.4 PRD,
actually no ISSUES from java.net are listed there).

----------------------------------------
In Java ME based test suites, we don't use the JTHarness' built-in agents and we
don't use the "Agent Monitor" tool, but this confuses the users since they think
that they need to use that Agent Monitor tool to monitor our, ME Framework-based
agents.

So far, we have only one workaround, to modify the javatest.jar itself, to
remove the Agent Monitor tool.

But this seems more like hack rather than a proper procedure, we really don't
like modifying the official JAR files.

So, we need a better way to control which tools are loaded and which are not
(and that includes the menus).

Maybe, there is something that I'm not aware of?

------- Additional comments from bkurotsu Tue Nov 17 18:12:49 +0000 2009 -------

There's no way to remove things yet. I agree that it is confusing for the Agent
Monitor to be there when it is not applicable.

------- Additional comments from bkurotsu Tue Dec 22 18:58:48 +0000 2009 -------

Please propose a solution for this. Perhaps an addition to FeatureManager.
Perhaps something which doesn't refer to the user interface itself, but perhaps
indicates whether JT should try to manager the test suite's agents or should
delegate that to the test suite's customization.

------- Additional comments from vsizikov Thu Nov 18 16:34:47 +0000 2010 -------

This is pretty important for ME FW. We were hoping that this has been fixed in 4.3.

Could you please add it to 4.4 list?
----------------------------------------------------------------