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/bl
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
LibreOffic
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 up
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
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
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
> >Ma
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,
>
>
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
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 fo
