<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body><a class="email" href="mailto:sbergman@redhat.com" title="Stephan Bergmann <sbergman@redhat.com>"> Stephan Bergmann</a> changed <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - JURT and JUH JARs contain bad class path declaration" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134248">bug 134248</a> <table border="1" cellspacing="0" cellpadding="8"> <tr> <th>What</th> <th>Removed</th> <th>Added</th> </tr> <tr> <td style="text-align:right;">CC</td> <td> </td> <td>noelgrandin@gmail.com, s.mehrbrodt@gmail.com </td> </tr></table> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - JURT and JUH JARs contain bad class path declaration" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134248#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - JURT and JUH JARs contain bad class path declaration" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134248">bug 134248</a> from <a class="email" href="mailto:sbergman@redhat.com" title="Stephan Bergmann <sbergman@redhat.com>"> Stephan Bergmann</a> <pre>(In reply to Alexander Veit from <a href="show_bug.cgi?id=134248#c3">comment #3</a>) > > Those entries are necessary so that native code used by those jars can be found. > > The usual way to provide a class path for a JVM instance is that the caller > specifies the class path to be uses before the JVM is started. > > When JARs try to pull in dependencies on their own they do not play nicely > together with other libraries the same JVM. That's not my understanding of how jars are supposed to work, but then again my understanding of the Java ecosystem is rather rusty and may be of no use here. Adding Noel and Samule in cc, maybe they can add something. > > The LibreOffice jars were never designed to be made available via Maven, > > outside the context of a LibreOffice installation. > > We use the libraries to utilize LibreOffice/OpenOffice as backend service > for rendering documents. I hope that such use cases are also supported by > the LibreOffice Java API. The "official" way is to access the jars provided by a LibreOffice installation via the SDK, see <<a href="https://api.libreoffice.org/">https://api.libreoffice.org/</a>>. > > I know that there have been efforts to make them available via Maven, > > but do not know how effective the results of those efforts were. > > I personally know next to nothing about Maven. > > The LibreOffice/OpenOffice libraries have been published and regularly > updated via Maven since 2007: > > <a href="https://mvnrepository.com/artifact/org.libreoffice">https://mvnrepository.com/artifact/org.libreoffice</a> > <a href="https://mvnrepository.com/artifact/org.openoffice">https://mvnrepository.com/artifact/org.openoffice</a> I assume that those have always been provided on an "appears to happen to work (more or less?)" basis.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>