RFR: 5904: Merge org.openjdk.jmc.ui.celleditors with org.openjdk.jmc.rjmx.ui.celleditors [v4]

Jie Kang jkang at openjdk.java.net
Fri Aug 20 15:28:27 UTC 2021


On Fri, 20 Aug 2021 13:06:04 GMT, Alex Macdonald <aptmac at openjdk.org> wrote:

>> So I do `a -> b` as in a depends on b, but I think you went the opposite is that right? I'm getting confused lol...
>> 
>> I think in the second case of consolidating celleditors into jmc.ui, a bunch of stuff appears that wasn't discussed before (rjmx.services, rjmx.subscription) Where are they coming from? Can they be moved to somewhere better?
>
> Er, yeah I guess I was thinking more of a flow diagram, I have it backwards here.
> 
> The reason it  looks like most of the classes were in rjmx.ui anyways was because they use classes from rjmx. So if the classes are moved from rjmx.ui to jmc.ui, they'd still need access to those (specifically rjmx.services and subscription.internal), so we'd have to add a dependency on those to jmc.ui.

Hm, okay. I took a step back and looked at the actual issue at hand.

I think it's more intended to migrate any cell editors from ooj.rjmx.ui to ooj.ui. The cell editors in ooj.rjmx.ui that have rjmx specific code (ie. import ooj.rjmx packages) should not be moved. (Should still be analyzed whether they can be modified and moved)

rjmx.ui is a specialized subset of ui for rjmx purposes, while ui is a general set for anybody to use (rjmx, flightrecorder, etc.). Why would we want to move things from ui to rjmx if they're not specialized for rjmx purposes? Especially as you note that there's already non-rjmx users of the things.

-------------

PR: https://git.openjdk.java.net/jmc/pull/271


More information about the jmc-dev mailing list