Re: Re: ship Maven meta information to ease creation of LO plugins with Maven
Hi all, thanks for all your answers. I hadn't noticed the change in Debian. But I am really glad that it also made its way upstream where all distributions can benefit from this change. Thanks for all your work Sebastian -- Web: http://www.crustulus.de | Blog: http://www.crustulus.de/cgi-bin/blog.cgi?de-0 Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html FreeDict: Free multilingual dictionary databases - http://www.freedict.org signature.asc Description: Digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: ship Maven meta information to ease creation of LO plugins with Maven
On 03/31/2014 09:46 PM, Sebastian Humenda wrote: 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. The LO jars generally need to be located at specific places within a LO installation tree. I am not sure that is compatible with the Maven concepts. Stephan ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: ship Maven meta information to ease creation of LO plugins with Maven
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 ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: ship Maven meta information to ease creation of LO plugins with Maven
Hi, On Tue, Apr 01, 2014 at 10:53:22AM +0200, Stephan Bergmann wrote: On 03/31/2014 09:46 PM, Sebastian Humenda wrote: 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. The LO jars generally need to be located at specific places within a LO installation tree. I am not sure that is compatible with the Maven concepts. isnt this what Rene already implemented for Debian (and thus Ubuntu) with: http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commit;h=1c130152fdb881db51543513ddafb212ff5c6df2 So do you want that to be upstreamed? Best, Bjoern ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: ship Maven meta information to ease creation of LO plugins with Maven
On 01/04/14 11:16, Bjoern Michaelsen wrote:
Hi,
On Tue, Apr 01, 2014 at 10:53:22AM +0200, Stephan Bergmann wrote:
On 03/31/2014 09:46 PM, Sebastian Humenda wrote:
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.
The LO jars generally need to be located at specific places within a
LO installation tree. I am not sure that is compatible with the
Maven concepts.
isnt this what Rene already implemented for Debian (and thus Ubuntu) with:
http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commit;h=1c130152fdb881db51543513ddafb212ff5c6df2
So do you want that to be upstreamed?
isn't this sort of the same as this upstream commit:
commit 78e4b97a18a18f84c228de64fc48cee48138fbfe
Author: David Ostrovsky da...@ostrovsky.org
AuthorDate: Sun Oct 27 20:32:40 2013 +0100
Set up tool chain to install LO artifacts in Maven repositories
Add path_to_libo/bin to your path.
After full LO compile, the LO Java artifacts can be installed in the
local
Maven repository:
mvn.py -a install -v 4.2.0 -s juh:jar:path_to/juh.jar
mvn.py -a install -v 4.2.0 -s jurt:jar:path_to/jurt.jar
mvn.py -a install -v 4.2.0 -s ridl:jar:path_to/ridl.jar
mvn.py -a install -v 4.2.0 -s unoil:jar:path_to/unoil.jar
With the artifacts installed this way, it is now possible
to consume LO artifacts from custom pom.xml:
[...]
properties
LibreOffice-Version4.2.0/LibreOffice-Version
/properties
[...]
dependencies
dependency
groupIdorg.libreoffice/groupId
artifactIdjuh/artifactId
version${LibreOffice-Version}/version
scopeprovided/scope
/dependency
dependency
groupIdorg.libreoffice/groupId
artifactIdjurt/artifactId
version${LibreOffice-Version}/version
scopeprovided/scope
/dependency
dependency
groupIdorg.libreoffice/groupId
artifactIdridl/artifactId
version${LibreOffice-Version}/version
scopeprovided/scope
/dependency
dependency
groupIdorg.libreoffice/groupId
artifactIdunoil/artifactId
version${LibreOffice-Version}/version
scopeprovided/scope
/dependency
/dependencies
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Aw: Re: ship Maven meta information to ease creation of LO plugins with Maven
Hi, The LO jars generally need to be located at specific places within a LO installation tree. I am not sure that is compatible with the Maven concepts. Is is. After some nudging I from Sebastian I did this in Debian: libreoffice (1:4.1.5-1) unstable; urgency=low * new upstream release * debian/patches/kde-yield-fix.diff: backport patch from LO 4.2.0 which rewrites Qt4 based nested yield mutex locking (closes: #728987, #723087) * debian/control.ure.in: - add missing second a in additional (closes: #734512) * debian/pom.*.xml.in, debian/*.poms, debian/rules: - install maven stuff for juh,jurt,ridl and unoil (based on the poms from http://bertfrees.github.io/snapshots/org/libreoffice/), thanks Sebastian Humenda * debian/tests/junit-subsequentcheck: - temporarily disable the report builder here; Depends: generation for -subsequentcheckbase somehow misses the needed build-deps now...?! -- Rene Engelhard r...@debian.org Tue, 11 Feb 2014 15:36:06 +0100 See https://packages.debian.org/sid/ure https://packages.debian.org/sid/libreoffice-common $ dpkg --contents ure_4.1.5-2_amd64.deb drwxr-xr-x root/root 0 2014-03-02 03:37 ./ drwxr-xr-x root/root 0 2014-03-02 03:36 ./usr/ drwxr-xr-x root/root 0 2014-03-02 03:36 ./usr/lib/ drwxr-xr-x root/root 0 2014-03-02 03:23 ./usr/lib/ure/ drwxr-xr-x root/root 0 2014-03-02 03:42 ./usr/lib/ure/lib/ -rw-r--r-- root/root 10440 2014-03-02 03:42 ./usr/lib/ure/lib/libunsafe_uno_uno.so -rw-r--r-- root/root 35584 2014-03-02 03:42 ./usr/lib/ure/lib/libtextinstreamlo.so -rw-r--r-- root/root105560 2014-03-02 03:42 ./usr/lib/ure/lib/libjvmfwklo.so -rw-r--r-- root/root 14656 2014-03-02 03:42 ./usr/lib/ure/lib/libaffine_uno_uno.so -rw-r--r-- root/root 43800 2014-03-02 03:42 ./usr/lib/ure/lib/libjavaloaderlo.so -rw-r--r-- root/root 10248 2014-03-02 03:42 ./usr/lib/ure/lib/libjpipe.so -rw-r--r-- root/root 27280 2014-03-02 03:42 ./usr/lib/ure/lib/libnamingservicelo.so -rw-r--r-- root/root 52040 2014-03-02 03:42 ./usr/lib/ure/lib/libinvocadaptlo.so -rw-r--r-- root/root170704 2014-03-02 03:42 ./usr/lib/ure/lib/libunoidllo.so -rw-r--r-- root/root 27032 2014-03-02 03:42 ./usr/lib/ure/lib/libjvmaccesslo.so -rw-r--r-- root/root146816 2014-03-02 03:42 ./usr/lib/ure/lib/libjavavmlo.so -rw-r--r-- root/root 64744 2014-03-02 03:42 ./usr/lib/ure/lib/libacceptorlo.so -rw-r--r-- root/root 60648 2014-03-02 03:42 ./usr/lib/ure/lib/libconnectorlo.so -rw-r--r-- root/root183432 2014-03-02 03:42 ./usr/lib/ure/lib/libreflectionlo.so -rw-r--r-- root/root 10288 2014-03-02 03:42 ./usr/lib/ure/lib/libjuh.so -rw-r--r-- root/root117624 2014-03-02 03:42 ./usr/lib/ure/lib/libjava_uno.so -rw-r--r-- root/root163224 2014-03-02 03:42 ./usr/lib/ure/lib/libbinaryurplo.so -rw-r--r-- root/root121680 2014-03-02 03:42 ./usr/lib/ure/lib/libinvocationlo.so -rw-r--r-- root/root 2258 2014-03-01 21:05 ./usr/lib/ure/lib/JREProperties.class -rw-r--r-- root/root 73496 2014-03-02 03:42 ./usr/lib/ure/lib/libsunjavapluginlo.so -rw-r--r-- root/root793736 2014-03-02 03:42 ./usr/lib/ure/lib/libbootstraplo.so -rw-r--r-- root/root 64152 2014-03-02 03:42 ./usr/lib/ure/lib/libjuhx.so -rw-r--r-- root/root 31456 2014-03-02 03:42 ./usr/lib/ure/lib/libuuresolverlo.so -rw-r--r-- root/root 31504 2014-03-02 03:42 ./usr/lib/ure/lib/libproxyfaclo.so -rw-r--r-- root/root126736 2014-03-02 03:42 ./usr/lib/ure/lib/libstocserviceslo.so -rw-r--r-- root/root 1072 2014-02-05 16:04 ./usr/lib/ure/lib/unorc -rw-r--r-- root/root179088 2014-03-02 03:42 ./usr/lib/ure/lib/libintrospectionlo.so -rw-r--r-- root/root 1060 2014-02-05 16:04 ./usr/lib/ure/lib/jvmfwk3rc -rw-r--r-- root/root 14648 2014-03-02 03:42 ./usr/lib/ure/lib/liblog_uno_uno.so -rw-r--r-- root/root 60320 2014-03-02 03:42 ./usr/lib/ure/lib/libgcc3_uno.so -rw-r--r-- root/root184520 2014-03-02 03:42 ./usr/lib/ure/lib/libstreamslo.so -rw-r--r-- root/root 27312 2014-03-02 03:42 ./usr/lib/ure/lib/libtextoutstreamlo.so -rw-r--r-- root/root 1685544 2014-03-02 03:42 ./usr/lib/ure/lib/libsal_textenclo.so drwxr-xr-x root/root 0 2014-03-02 03:23 ./usr/lib/ure/share/ drwxr-xr-x root/root 0 2014-03-02 03:37 ./usr/lib/ure/share/java/ drwxr-xr-x root/root 0 2014-03-02 03:33 ./usr/lib/ure/share/misc/ -rw-r--r-- root/root 7885 2014-03-01 21:44 ./usr/lib/ure/share/misc/services.rdb -rw-r--r-- root/root 57175 2014-03-02 02:48 ./usr/lib/ure/share/misc/types.rdb -rw-r--r-- root/root 2311 2014-02-05 16:04 ./usr/lib/ure/share/misc/javavendors.xml drwxr-xr-x root/root 0 2014-03-02 03:42 ./usr/lib/ure/bin/ -rwxr-xr-x root/root 1508 2014-02-05 16:04 ./usr/lib/ure/bin/startup.sh -rwxr-xr-x root/root 89080 2014-03-02 03:42 ./usr/lib/ure/bin/uno.bin -rwxr-xr-x root/root 18960 2014-03-02 03:42 ./usr/lib/ure/bin/regmerge
Aw: Re: ship Maven meta information to ease creation of LO plugins with Maven
Hi, Is is. After some nudging I from Sebastian I did this in Debian: [...] https://packages.debian.org/sid/libreoffice-common https://packages.debian.org/sid/libreoffice-java-common, obviously. Regards, Rene ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Aw: Re: ship Maven meta information to ease creation of LO plugins with Maven
Hi, isnt this what Rene already implemented for Debian (and thus Ubuntu) with: http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commit;h=1c130152fdb881db51543513ddafb212ff5c6df2 So do you want that to be upstreamed? isn't this sort of the same as this upstream commit: commit 78e4b97a18a18f84c228de64fc48cee48138fbfe Author: David Ostrovsky da...@ostrovsky.org AuthorDate: Sun Oct 27 20:32:40 2013 +0100 Set up tool chain to install LO artifacts in Maven repositories Seems so, yes. Of course I didn't see that when I did that as I was doing this in 4.1.x first. Thanks for the pointer, will use that one in 4.2.x. Regards, Rene ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
ship Maven meta information to ease creation of LO plugins with Maven
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 -- Web: http://www.crustulus.de | Blog: http://www.crustulus.de/cgi-bin/blog.cgi?de-0 Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html FreeDict: Free multilingual dictionary databases - http://www.freedict.org signature.asc Description: Digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
