I think that we should provide the ability to expose JMX runtime controls in erma-lib. I think that we should keep erma-api as lean as possible, but there are many OS projects that use JMX as a means of exposing controls. The actual means of exposing the controls is up for debate.
Matt On Wed, Dec 10, 2008 at 2:25 PM, Ray Krueger <[EMAIL PROTECTED]> wrote: > >>> The error is: > >>> build.xml:99: taskdef A class needed by > >>> org.apache.commons.compiler.AttributeCompiler cannot be found: > >>> xjavadoc/ant/XJavadocTask > >>> > >>> The commons-attributes task is currently commented out so that the rest > of > >>> the build works. > > > > Why the hell are we trying to use commons-attributes anyway? Maybe > > Orbitz should keep that old junk to itself :P > > > > Was just chatting with Matt Kemp offline... > The commons-attributes noise is being added to Erma classes to expose > them as MBeans. I, personally, disagree with this entirely. > On one hand, I dont' think we should be adding JMX stuff to it at all, > and on the other hand we definitely shouldn't be doing it with > commons-attributes. JMX and commons-attributes are Orbitz specific use > cases in summary. >
_______________________________________________ Mailing list: https://launchpad.net/~erma-core Post to : erma-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~erma-core More help : https://help.launchpad.net/ListHelp
