xardion has quit [Remote host closed the connection]
xardion has joined #jruby
dopplergange has quit [Quit: ZNC 1.7.5 - https://znc.in]
dopplergange has joined #jruby
<headius[m]>
enebo: g'day
<venkatkms[m]>
@headius: sorry to trouble you. How do i build a distribution (the full binary) for jruby? The mvn install only built the jruby-complete.jar. Thank you.
<headius[m]>
venkatkms: mvn -Prelease should build everything
<headius[m]>
if you just want the JRuby dir set up to be usable then just 'mvn' should do it
<headius[m]>
I am happy to announce that -e 1 running without any module flags displays no warnings
<headius[m]>
enebo: so we have some marching orders before fall... Java 16 will lock down illegal access from unnamed modules, which means we probably need to get our overall module game in better shape
<headius[m]>
the jar in the JRuby dist may be better transitioning toward a simple jruby-core jar with the other libraries alongside it...that will let us use the same module opens/exports config for both the core jar and the dist setup
<headius[m]>
I am not sure how that will impact startup though... going from one jar to several
<headius[m]>
as it is now we have to have two sets of rules in some places because the code might be running as org.jruby.dist module or org.jruby.core module
<headius[m]>
if it were always core we'd have a single path
subbu is now known as subbu|afk
ur5us has joined #jruby
<enebo[m]>
headius: yeah I was going to ask how long term this solution would be
<enebo[m]>
16 is the deadline then
<headius[m]>
well it's a deadline of a sort
<headius[m]>
at 16 all the core JDK stuff will be closed by default
<headius[m]>
when running at command line we already open up what we need
<enebo[m]>
so we can just set up proper opens for that
<headius[m]>
but this will affect embedding if that embedding doesn't open things up or doesn't put us in module path
<enebo[m]>
and then use the trick a while long outside that
<headius[m]>
there's no easy way to make sure people use our jar with the proper opens other than warning
<headius[m]>
(or failing I suppose)
<enebo[m]>
I feel like embedding is special and we need not prevent warnings there but make it easy to get the proper magic options so they can continue running
<headius[m]>
so basically unmoduled jruby jar will basically go to degraded functionality, which means no real fileno etc
subbu|afk is now known as subbu
<headius[m]>
enebo: I have pushed my last commit for the illegal access PR