Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] OSGi tests and JMX

Hi Greg,
OK understood; thanks for the explaination. Updating my svn and trying to make them work again.

On Fri, Jan 7, 2011 at 1:41 AM, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:
Hugues ,

I've had to disable the osgi tests because of a fundamental lack of
understanding of how to make them work after I've refactored the JMX

Previously the JMX module contained our JMX infrastructure
(ObjectMBean and container), plus it held some specific MBeans for
other modules and all the meta data for all dynamically generated
This resulted in cyclic dependencies because JMX had to depend on
modules for which it was implementing MBeans, but then we have many
tests that include JMX as a dependency.

So I have refactored so that jetty-jmx contains just our JMX
infrastructure and every module then contains it's own JMX meta data
and MBeans (if any).  The modules that have MBean classes now depend
on jetty-jmx as an optional dependency.     Unfortunately this does
not appear to get reflected in the OSGi manifests and the tests are
failing saying that it cannot resolve jetty-jmx.    I've tried to
force jetty-jmx as a real dependency of jetty-osgi boot, but that does
not appear to help.

As I need to make this change to progress on some other fronts, for
now I've just commented out the osgi tests. Obviously this is not good
and I have probably broken any thing else that uses the osgi modules.
Can you ping me when you are online and we can work out how to fix


Back to the top