Hi Sebastian,
May be this maven plugin for building LO extensions could interest you:
https://github.com/cbosdo/maven-ooo-plugin
I didn't touch this code since ages, but if it can help you, feel free
to patch it ;)
--
Cedric
On Mon, 2014-03-31 at 21:46 +0200, Sebastian Humenda wrote:
Hi,
to build software with Maven, you have to provide meta information (a pom.xml)
to each jar, which is a dependency of your software. In turn, the build system
Maven with automatically figure out which jar to fetch from where and in which
version. To simplify the creation of Java dependencies for LO and to ease also the
packaging of LO extension in Debian/Ubuntu, it would be of much help, if you
could ship those pom.xml for this use case with the source. This meta
information is easy and quick to generate and the only maintenance overhead is
the version number increase at each LO release. You don't need to also use Maven
for building LO, you just have to ship one pom.xml for one jar file.
Not only Debian/Ubuntu would benefit from this little adjustment, also other
projects could use the provided meta information. It would be of course even
greater to have the shipped jar files together with the meta information in a
online repository, whereas this is not as important as the first issue. Such a
repository existed for OpenOffice before they moved to Apache (see
http://mvnrepository.com/artifact/org.openoffice).
Thanks!
Sebastian
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.