Date: prev next · Thread: first prev next last
2019 Archives by date, by thread · List index


Hey,

On Sat, Mar 30, 2019 at 6:22 AM Andrés Maldonado <amaldonado@linagora.com>
wrote:

Hello,

I was working on EasyHack 122169
<https://bugs.documentfoundation.org/show_bug.cgi?id=122169> and
submitted a patch <https://gerrit.libreoffice.org/#/c/69914/> to Gerrit,
but the Jenkins build failed because the commit
<https://cgit.freedesktop.org/libreoffice/cppunit/commit/?id=48145587c4c2dc4f1e07d83073e136336c81ce79>
that adds the CPPUNIT_TEST_FIXTURE macro is not yet on a released version
of CppUnit. Would it be possible to make a cppunit-1.14.1 release ? :)


There won't be a 1.14.1 release. At some point I'll release 1.15 but need
more time to polish the release. Currently the plan is not to include
CPPUNIT_TEST_FIXTURE in any future releases. I have realized that
CPPUNIT_TEST_FIXTURE is not a good API for cppunit.


I would also like to suggest to create a page with the latest
documentation ;) (the most recent doc that i found online
<http://cppunit.sourceforge.net/doc/lastest/index.html> is from the
original project, for version 1.10.2)


There is an up-to-date set of the documentation at
https://people.freedesktop.org/~mmohrhard/cppunit/index.html

Regards,
Markus


Cheers,
Andrés Maldonado
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

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.