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, but just modified the upload, to include the aar together with the primary jar, javadocs and source. You can see for the jna library itself: https://repo1.maven.org/maven2/net/java/dev/jna/jna/5.1.0/ JNA uses the maven deploy plugin with the deploy-file goal and uploads the files together (from the ant build script): <artifact:mvn failonerror="true"> <arg value="org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file"/> <arg value="-Durl=${maven-snapshots-repository-url}"/> <arg value="-DrepositoryId=${maven-snapshots-repository-id}"/> <arg value="-DpomFile=${pom}"/> <arg value="-Dfile=${dist-jar}"/> <arg value="-Dfiles=${maven-sources-jar},${maven-javadoc-jar},${dist-aar}"/> <arg value="-Dtypes=jar,jar,aar"/> <arg value="-Dclassifiers=sources,javadoc,"/> </artifact:mvn> Maybe that helps Matthias Am Sonntag, den 09.12.2018, 20:36 +0100 schrieb Johan Vos: > 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 at 11:20 PM Scott Palmer <swpal...@gmail.com> wrote: > > > Is there a reason not to make the jmod files available as artifacts on > > Maven Central?
