https://bugs.documentfoundation.org/show_bug.cgi?id=165774
--- Comment #4 from Stephan Bergmann <[email protected]> --- (In reply to prrvchr from comment #3) > The PR I'm proposing allows an extension to use a Java instrumentation agent > just by installing it. The user doesn't have to do anything else... I'm not convinced. For one, my naive understanding is that Java agents are a means for debugging and monitoring. Something done by technically skilled people, for which the existing way of enabling such a Java agent should presumably be tolerable. But, more importantly, for another, and as I already had tried to explain elsewhere: The LO code instantiating a JVM (jvmaccess, jvmfwk, stoc; all part of URE) cannot access the LO configuration (configmgr, officecfg; both not part of URE). So, you would first need to address that if using officecfg is a central piece of what you want to achieve here. (And it wasn't clear to me until your comment 3 above that that shall indeed be a central piece here.) But _if_ we ever wanted to let the LO code instantiating a JVM have access to the LO configuration, I would rather move all of LO's JVM configuration machinery over to the configmgr/officecfg-based LO configuration, instead of arbitrarily having a single InstrumentationAgentArchive in officecfg and the rest stay in the existing JVM configuration machinery. -- You are receiving this mail because: You are the assignee for the bug.
