Apache OpenOffice (AOO) Bugzilla – Issue 128365
Create Java UNO artifacts during build process suitable for Apache Nexus or Maven Central
Last modified: 2021-05-27 21:31:32 UTC
This issue is to document work to include the copying of Java UNO jars and the creation of Javadoc and Source jars for them during the build process suitable for uploading to Apache Nexus for distribution. This allows the artifacts to be used in build systems like Maven and Gradle or scripting languages like Groovy that download artifacts. The main purpose of the work is to have these jar artifacts pre-built and ready for release at the same time as a release of OpenOffice. Previously this was done manually after a release requiring a separate vote but this is not ideal. The manual process is described in the Maven Bundles wiki article [1]. Currently this work is being done on a fork of OpenOffice here [2] and a pull request will be used when completed. [1] https://wiki.openoffice.org/wiki/Uno/Java/MavenBundles [2] https://github.com/cbmarcum/openoffice/tree/mavenjars
This work is now in the maven-jars branch [1]. [1] https://github.com/apache/openoffice/tree/maven-jars
This work is now in maven-jars-2 [1]. I've been able to get many the additional source and javadoc jars created during build but I'm stalled on getting them into the distribution package. [1] https://github.com/apache/openoffice/tree/maven-jars-2