Alternative to fatJar - modular solution?
Samuel Audet
samuel.audet at gmail.com
Wed Oct 27 14:00:07 UTC 2021
Yes, that kind of thing, Mike, thanks for the good example! I'm doing
something very similar with JavaCPP, but at the library level rather
than at the application level.
Ok, Dalibor, I'll try to stay technical, so here's a couple of technical
question I have for at least you and Ioi. There's a lot of tools like
those that bundle JAR files, native libraries, various resources such as
JavaScript and Python scripts, and what not, and that includes Android,
which runs on over 3 billion devices apparently:
https://www.theverge.com/2021/5/18/22440813/android-devices-active-number-smartphones-google-2021
Given that this kind of feature is almost essential to pretty much every
application out there these days, why isn't OpenJDK expending more
effort into the available options to standardize all that?
For example, something cool that Android has started doing recently is
to bundle native libraries uncompressed by default. This allows Linux to
load them--without extracting them--directly from the APK file (which is
just a glorified ubar JAR file for an Android application)! I can see
OpenJDK doing the same thing for bundled JAR files, as Ioi mentioned
earlier, allowing us to scan them without extracting them, right?
That's the kind of thing I'd like to work on, but from what I
understand, it's rather hard to be become part of "OpenJDK" since we
essentially have to become Oracle employees, or something close, handing
over all copyrights... Where does the "community" fit in this?
Samuel
On 10/14/21 19:54, Mike Hearn wrote:
> It's worth noting that before he worked on Loom, Ron Pressler wrote
> Capsule, which is a kind of uber-fat-jar system that embeds JARs within
> JARs:
>
> https://github.com/puniverse/capsule
>
> The website is offline now but it had a lot of features, including the
> ability to extract shared libraries from the 'capsule'. It worked by
> extracting files to a cache directory and running them from there. So, Ron
> might have some insight to offer here, if asked.
>
More information about the jigsaw-dev
mailing list