Feedback on JMX-4

[Tyler Hobbs]

Currently, the contrib JMX library only has two options for reading
the attributes of an MBean: read only a single attribute, or read all
of them. It would be useful to have some middle ground here.

I've opened JMX-4 and attached a patch that would allow multiple
attributes of an MBean to be read with a single call. Your feedback
would be appreciated.

(On a related note, it looks like JMX-1 and JMX-2 haven't gotten any
attention. Is there a way I could help move those forward?)

Thanks,
- Tyler

[Stuart Halloway]

I don't want to be the maintainer for JMX -- would appreciate anybody who has commit access on contrib reviewing and pushing these tickets as appropriate.

Thanks,
Stu

[Kevin Downey]

perhaps some new contrib committers could be minted

> --
> You received this message because you are subscribed to the Google Groups "Clojure Dev" group.
> To post to this group, send email to cloju...@googlegroups.com.
> To unsubscribe from this group, send email to clojure-dev...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/clojure-dev?hl=en.
>

--
And what is good, Phaedrus,
And what is not good—
Need we ask anyone to tell us these things?

[Nick Bailey]

I would be glad to help out with maintaining java.jmx. (I'm the guy
who created JMX-1 and JMX-2)

I'm not sure what the process here is for adding general contrib
committers vs adding a commiter to a specific contrib library. It
sounds like we need someone to take ownership of the jmx project
though.

[Tyler Hobbs]

On Feb 10, 4:19 pm, Kevin Downey <redc...@gmail.com> wrote:
> On Wed, Feb 8, 2012 at 2:27 PM, Stuart Halloway
>
>
> <stuart.hallo...@gmail.com> wrote:
> >> Currently, the contrib JMX library only has two options for reading
> >> the attributes of an MBean: read only a single attribute, or read all
> >> of them.  It would be useful to have some middle ground here.
>
> >> I've opened JMX-4 and attached a patch that would allow multiple
> >> attributes of an MBean to be read with a single call.  Your feedback
> >> would be appreciated.
>
> >> (On a related note, it looks like JMX-1 and JMX-2 haven't gotten any
> >> attention.  Is there a way I could help move those forward?)
>
> >> Thanks,
> >> - Tyler
>
> > I don't want to be the maintainer for JMX -- would appreciate anybody who has commit access on contrib reviewing and pushing these tickets as appropriate.
>
> > Thanks,
> > Stu
>
> perhaps some new contrib committers could be minted
>

Any thoughts on how to proceed with this?

[Nick Bailey]

I work with Tyler and we would like to be able to help reach a
solution here, rather than throwing a jar with jmx fixes onto clojars
and forgetting about these tickets. It seems like the JMX library
probably isn't heavily used since no one else has seen these problems,
but it would still be good to get these changes in.

Perhaps we can use this as an opportunity for setting a precedent for
situations like this where there is a library in contrib and the
current maintainer isn't able to own that project (due to time
constraints or whatever other reasons). It seems to me like there
isn't really a process for a situation like that currently.

It could be that since java.jmx doesn't really have an actual
maintainer and *seems* to be not heavily used, it should be dropped as
an official contrib library. From what I understand, the main factor
in deciding migration from monolithic contrib to modular contrib is
that someone was able to take active ownership of each contrib module.
I'm not really sure that is the best solution since jmx is a pretty
big/useful part of java interop, it is an option though.

The other course of action I guess is to better establish the process
for transferring ownership of modules like this. If we want to keep
jmx as a contrib module we either need someone who has some time and
is a contrib committer to volunteer to take over ownership of the jmx
project, or add new committers to the jmx repo. As I said before, I
would be willing to help but maybe the rest of clojure/dev is more
comfortable with someone who already has contrib commit access taking
over.

Thanks guys,
Nick

[Sean Corfield]

On Tue, Feb 21, 2012 at 12:59 PM, Nick Bailey <nickm...@gmail.com> wrote:
> Perhaps we can use this as an opportunity for setting a precedent for
> situations like this where there is a library in contrib and the
> current maintainer isn't able to own that project (due to time
> constraints or whatever other reasons). It seems to me like there
> isn't really a process for a situation like that currently.

The process is: someone else volunteers to take it over (and then the
wizards behind the curtain set up the appropriate github, JIRA,
Confluence and build server permissions). Guidelines and process are
described here:

http://dev.clojure.org/display/doc/Guidelines+for+Clojure+Contrib+committers

(yes, I finally got around to putting the setup process on the wiki
like I promised to do at the conj - sorry!)
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/

"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)