On 31/01/2025 17:33, Code Ranger wrote:
I am sure, that if it is necessary to use agent and java instrumentation
to make this the simplest configuration work, then it simply means, that
something is wrong here. Maybe two many constrains?
Hmm, it is not always good to be too sure about things.
> On 31 Jan 2025, at 18:25, Code Ranger wrote:
>
>
>
> On 1/31/25 19:54, Ron Pressler wrote:
>>>
>>> Unfortunately, this is correct.
>>>
>>> I am sure, that if it is necessary to use agent and java instrumentation to
>>> make this the simplest configuration work, then it simply means, that
On 1/31/25 19:54, Ron Pressler wrote:
Unfortunately, this is correct.
I am sure, that if it is necessary to use agent and java instrumentation to
make this the simplest configuration work, then it simply means, that something
is wrong here. Maybe two many constrains?
Manipulating a module
It seems the JLine maintainers were concerned about depending on the
internals of a separate project (jansi), because "to minimize the
maintenance cost, Jansi has been merged into JLine 3.25."
(https://github.com/jline/jline3).
That's a good step because it saves people who are not maintainers
> On 31 Jan 2025, at 17:33, Code Ranger wrote:
>
>
>
> On 1/31/25 19:23, Ron Pressler wrote:
>>
>>
>>> On 31 Jan 2025, at 16:49, Code Ranger wrote:
>>>
>>>
>>> 1. we don't have access to the boot layer controller and we received a
>>> categorical refusal to grant access to it.
>>>
>> T
On 1/31/25 19:23, Ron Pressler wrote:
On 31 Jan 2025, at 16:49, Code Ranger wrote:
1. we don't have access to the boot layer controller and we received a
categorical refusal to grant access to it.
That is incorrect. The API for controlling modules in the boot layer has been
available sinc
> On 31 Jan 2025, at 16:49, Code Ranger wrote:
>
>
> 1. we don't have access to the boot layer controller and we received a
> categorical refusal to grant access to it.
That is incorrect. The API for controlling modules in the boot layer has been
available since JDK 9, using the very mechan
Thank you for your suggestion.
jansi should be placed in the boot layer, because it is also used by log4j2,
that also should be in the boot layer.
I think (I may be wrong, because I am not a JPMS guru like jigsaw team members)
the problem arises due to two serious constraints:
1. we don't have
AFAIK it cannot be done with `jansi` in your boot layer. One solution would
be to put it into a child layer, which will allow you to access the
`Controller` for it, which you can then use to add the export manually
after defining the `jline3` module in its sub-layer. Otherwise, `jansi`
would have t
Hello all.
I have a boot layer with `org.fusesource.jansi` module a child layer with
jline3 module. Jline3 wants to use jansi:
Caused by: java.lang.IllegalAccessError: class
org.jline.terminal.impl.jansi.JansiTerminalProvider (in module org.jline)
cannot access class org.fusesource.jansi.inte
10 matches
Mail list logo