> I don’t see that as a problem as new versions can be uploaded as
required.
Don't you think it would be an issue if Oracle decided to change the JAR
format from ZIP to something else?
I agree with the rest of your reply though.
On Mon, Dec 10, 2018 at 1:16 PM August Nagro wrote:
> I wouldn't
Inline
> On Dec 10, 2018, at 2:16 PM, August Nagro wrote:
>
> I wouldn't recommend publishing JMOD files on maven central since the file
> format is not yet stable (based on zip currently, but ideally will change to
> better compression in the future). JMOD seems to be 'unfinished business'
I wouldn't recommend publishing JMOD files on maven central since the file
format is not yet stable (based on zip currently, but ideally will change
to better compression in the future). JMOD seems to be 'unfinished
business' from JPMS.
Ex,
https://stackoverflow.com/questions/44732915/why-did-java
Hi Johan,
I was in a similar situation for JNA (Java Native Access) and found,
that sonatype accepts other package types than jar/javadoc/sources.
To support opening JNI libraries, the native parts need to be packed
differently. This packaging is an "aar" (Android Archive). I did not
ask sonatype
Hi Scott,
I got the use case. I think it should be possible, although in general
uploading to the OSS sonatype repository requires uploading jars for the
classes, sources and javadoc. There is no procedure yet (afaik) for
uploading mods, but we can see if that works.
- Johan
On Fri, Dec 7, 2018
Is there a reason not to make the jmod files available as artifacts on
Maven Central?
The idea being that I can then use dependency management in my Gradle
script and not require the extra setup and configuration of a JavaFX SDK -
yet still be able to use the jmod files as input to jlink. I would
