Hello All,
BACKGROUND
In my work on the groovy-uno extensions to the Java UNO api's I found a
need to bootstrap the office from groovy scripts and unit tests
where the UNO jars are not on the classpath in the same place as the
office executable.
The solution I found was an old post in the OpenOffice forum with a
downloadable bootstrapconnector.jar with source code [1].
This solution allows bootstrapping the office by passing a string
representing the path to the office executable to the method.
ACTION
I have obtained permission from the author to use the code by our
project and under the AL 2.0 license and documented it with the AOO PMC.
I created a bugzilla issue [2] to document the upload to SVN under
devtools [3] and apply the license headers.
The code is setup by me as a Gradle built project and I have included a
README.md file describing build instructions, usage, and credits in
addition to adding the META-INF/LICENSE, NOTICE, and CREDIT files that
will build into the jar file.
NOT YET DONE
I would like to create a Maven bundle,jar containing signed source,
classes, and javadoc jars and submit this to our Maven repository
similar to the recently submitted Java UNO jars.
QUESTION
Since this is code not included with the voted upon AOO 4.1.2 release,
do I need to call a vote or is lazy-consensus satisfactory since this is
a developer tool similar to the AOO-Netbeans Integration plugin?
[1] https://forum.openoffice.org/en/forum/viewtopic.php?t=2520
[2] https://bz.apache.org/ooo/show_bug.cgi?id=126807
[3]
https://svn.apache.org/repos/asf/openoffice/devtools/bootstrap-connector/trunk/
Thanks,
Carl
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
