Also, JMX code is already in its own package :)
On 30 March 2014 13:16, Matt Sicker <[email protected]> wrote: > JMS, not JMX. > > > On 30 March 2014 13:11, Ralph Goers <[email protected]> wrote: > >> What JaveEE APIs? JMX was moved to Java SE in 1.5 and 1.6. >> >> I’m not sure I like the mbeans registering automatically but oh well. >> >> Ralph >> >> On Mar 30, 2014, at 10:52 AM, Matt Sicker <[email protected]> wrote: >> >> Since JMS depends on Java EE APIs, it would make sense to place them in >> their own packages similar to how the db code is handled. I know they work >> fine as is, but it makes it easier to segregate optional dependencies. This >> would be useful for OSGi so that we can use the full set of metadata >> available without requiring all the optional dependencies in the >> Import-Package attribute. >> >> -- >> Matt Sicker <[email protected]> >> >> >> > > > -- > Matt Sicker <[email protected]> > -- Matt Sicker <[email protected]>
