Hello!
As a long time Java developer, I've only ever had to deal with signing
jar files. I can obviously sign jar files once on whatever platform I
choose to use to build the code, and then distribute the jars to all
platforms. Build once, run everywhere, etc.
However, now that jlink exists, as a
No matter what I do, there's always one document I didn't look at. :/
As usual, thank you very much!
On 11.02.2018 21:48, Alan Bateman wrote:
>
>
> On 11/02/2018 15:31, Nicolai Parlog wrote:
>> :
>> I interpreted this to mean that, without registering services, named
>> modules can only load b
Hi!
I think recording module version information is a really
underappreciated feature in Java 9+. The module's own version shows up
in many places, which I like. I think it could be added to `java
--show-module-resolution`, too.
It is much harder to access the versions of the dependencies agains
2018/2/11 23:10:46 -0800, Michal Vala :
> On 02/10/2018 11:25 AM, Alan Bateman wrote:
>> ...
>>
>> I think the `jimage extract --dir ` scenario
>> needs
>> discussion. If is a non-directory file then jimage has to
>> fail,
>> I don't expect disagreement on that. For the case where it is an e
2018/2/12 3:44:07 -0800, Mark Raynsford :
> ...
>
> Are there any plans to implement anything that's capable of signing
> macOS binaries and resources in a platform-independent way so that
> jlink-produced distributions can work without warnings?
No.
>
In the process of adapting pure reflective code (a Rexx-Java bridge) to use
MethodHandles on Java 9
instead, everything seems to be working out so far.
In principle all invocations on the Java side are carried out by first using
java.lang.reflect
(Field, Method, Constructor) using the supplied a
On 2/12/18 12:36 PM, Vitaly Davidovich wrote:
Hi all,
I'm not sure if core-libs is the right mailing list for jigsaw/modules
questions these days (rather than jigsaw-dev), so please feel free to
forward this there if it's the more appropriate list.
cc'ing jigsaw-dev
I have the following c
