Team,
I think i got the solution. I added my jar into a lib directory, added it
as library in my eclipse project, and added it to package.properties.
This worked out.
On Wed, Oct 9, 2019 at 4:07 PM Harish Kumar <harishbhaskaruni@gmail.com>
wrote:
Hi Samuel,
Thank you for pointing that out. Now i see that my jar is getting
packaged in the oxt. Unfortunately my code still
says java.lang.ClassNotFoundException.
Cant go beyond this point.
On Wed, Oct 9, 2019 at 3:13 PM Samuel Mehrbrodt <s.mehrbrodt@gmail.com>
wrote:
Hi Harish,
https://github.com/smehrbrodt/libreoffice-starter-extension#development-hints
says:
*If you add non-code files (or an external .jar) to your extension, you
need to mention them in package.properties, else they won't be included in
the packaged extension.*
Does that help?
Regards
Samuel
Am 09.10.19 um 11:36 schrieb Harish Kumar:
Hi Team,
I am writing an extension for LO and i need to use some external jars in
my project.
I am using LOEclipse plugin for my development. But while running the
extension, i am unable to get the referenced external jars. Seems like they
are not packed into the extension.
Can you please help me on how to pack my external jars to make the
extension. ( using LOEclipse)
--
Best Regards,
Harish Kumar.B
_______________________________________________
LibreOffice mailing
listLibreOffice@lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/libreoffice
--
Best Regards,
Harish Kumar.B
--
Best Regards,
Harish Kumar.B
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.