Date: prev next · Thread: first prev next last


Hi Svante,

it contains JavaDoc:
https://repo1.maven.org/maven2/org/odftoolkit/odfdom-java/1.0.0-BETA1/odfdom-java-1.0.0-BETA1-javadoc.jar

I saw that file; I guess my point was that it does not actually contain any javadoc documentation. 
I unpacked it and there is not much in there, just some images. It's only 665KB; in contrast the 
0.9.0-RC1 javadoc here

  https://repo1.maven.org/maven2/org/odftoolkit/odfdom-java/0.9.0-RC1/

is 22MB in size.

Grüße nach Berlin,
Malte.


On 28 Aug 2021, at 22:14, Svante Schubert <svante.schubert@gmail.com> wrote:

Hello Malte,

it contains JavaDoc:
https://repo1.maven.org/maven2/org/odftoolkit/odfdom-java/1.0.0-BETA1/odfdom-java-1.0.0-BETA1-javadoc.jar
you might unpack
<https://docs.oracle.com/javase/tutorial/deployment/jar/unpack.html>.
Still, you could always build it for yourself from the latest sources with 'mvn
javadoc:javadoc
<https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html>'
resulting javadoc in the target or target/site build directory.

Enjoy your weekend,
Svante

Am Sa., 28. Aug. 2021 um 12:40 Uhr schrieb Malte Stien <malte@stien.de>:

Hi Svante,

Thank you. Good hint; I have switched to 1.0.0-beta as per your suggestion.

That said, I noticed the javadoc JAR hosted here

 https://repo1.maven.org/maven2/org/odftoolkit/odfdom-java/1.0.0-BETA1/

does not actually contain any Javadoc. Is that hosted anywhere or
downloadable from anywhere? Or do I have to build that myself?

Thank you,
Malte.

On 27 Aug 2021, at 17:14, Svante Schubert <svante.schubert@gmail.com>
wrote:

Hi Malte,

you might want to use the master branch or

https://mvnrepository.com/artifact/org.odftoolkit/odfdom-java/1.0.0-BETA1

As there are several years of development between 0.9.0 and 1.0.0.
Version 1.0.0 enables the concept of the change - during work for a
company
adding office browser support.

Best regards,
Svante

Am Fr., 27. Aug. 2021 um 01:29 Uhr schrieb Malte Stien <malte@stien.de>:

Great. Thank you all so much. I managed to generate my first
ODFTextDocument using 0.9.0-RC1.

I will progress down this path and am sure to be back with more
questions.

Keep the good work up! It's great that this exists.

Danke,
Malte.

On 27 Aug 2021, at 00:41, Hans Grimmelshausen <farold@mail.de> wrote:

Thank you Michael for the docu correction.

Could you, or Svante, also please correct the download links for the
bundles, at:
https://tdf.github.io/odftoolkit/downloads.html

Under the topic: ODF Toolkit Release Bundles (latest)
All the three download-links – sources, binaries, documentation (and
their sha) – for each version (0.10.0 and 0.9.0) result in the error
message "not found".

Thanks for all your good work for Libreoffice and its important
Odftoolkit!

Grüße,
Hans



Am 26.08.2021 um 16:11 schrieb Michael Stahl:
On 26.08.21 11:49, Michael Stahl wrote:
On 26.08.21 10:01, Malte Stien wrote:
I started using the publicly hosted java docs here:
https://odftoolkit.org/api/odfdom/index.html. What version are they
for?
They are telling me the OdfTextDocument has been deprecated in favour of
"org.odftoolkit.simple.TextDocument in Simple API", but then again that
has
been deprecated, right?

yes, that was bug https://github.com/tdf/odftoolkit/issues/56

i don't actually know what's on odftoolkit.org, that server is
manually maintained by TDF infra and likely outdated.

the most up to date is here, deployed automatically from the master
branch:

https://tdf.github.io/odftoolkit/

... although the JavaDoc in there is also outdated, last updated in
2019 :(

uh... well... if you build the source via maven the current JavaDoc
is
generated...

not even that is the case, you have to invoke "mvn javadoc:javadoc" to
get it

but i've updated it now in the master branch and the JavaDoc on
https://tdf.github.io/odftoolkit/ should be up to date now :)




--
To unsubscribe e-mail to: dev+unsubscribe@odftoolkit.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:
https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.odftoolkit.org/dev/
Privacy Policy: https://www.documentfoundation.org/privacy


--
To unsubscribe e-mail to: dev+unsubscribe@odftoolkit.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:
https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.odftoolkit.org/dev/
Privacy Policy: https://www.documentfoundation.org/privacy


--
To unsubscribe e-mail to: dev+unsubscribe@odftoolkit.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:
https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.odftoolkit.org/dev/
Privacy Policy: https://www.documentfoundation.org/privacy



-- 
To unsubscribe e-mail to: dev+unsubscribe@odftoolkit.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.odftoolkit.org/dev/
Privacy Policy: https://www.documentfoundation.org/privacy


-- 
To unsubscribe e-mail to: dev+unsubscribe@odftoolkit.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.odftoolkit.org/dev/
Privacy Policy: https://www.documentfoundation.org/privacy

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.