#. extracted from dictionaries/cs_CZ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: https://bugs.libreoffice.org/enter_bug.cgi?product=LibreOffice&bug_status=UNCONFIRMED&component=UI\n" "POT-Creation-Date: 2017-10-04 11:48+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Accelerator-Marker: ~\n" "X-Generator: LibreOffice\n" #: description.xml msgctxt "" "description.xml\n" "dispname\n" "description.text" msgid "Czech spell check dictionary, hyphenation rules and thesaurus" msgstr "" s. This patch adds two new make defines to be used used by Java UNO and UNO API tests: - gb_JunitTest_set_unoapi_test_defaults - gb_JunitTest_set_unoapi_test_class_and_jars The first one will deduce most defaults from the test name, but still allows to optionally override most settings. If a test doesn't match the default at all, the 2nd define still shares the common jar files and the main Java UNO class, so the second define adds these to your makefile. The real fix is to add juh.jar to gb_JunitTest_use_jars. Change-Id: I4342fdac5e31f85ea18fb4268e13c287a7adc2b7 Reviewed-on: https://gerrit.libreoffice.org/63118 Tested-by: Jenkins Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de> 
Originally I just wanted to add the juh.jar to the list of jars
of the UNO API tests, but this became tedious work, so after the
first few files I decided to replace the similiar makefiles with
a common define for the *_unoapi* tests.

This patch adds two new make defines to be used used by Java UNO
and UNO API tests:
- gb_JunitTest_set_unoapi_test_defaults
- gb_JunitTest_set_unoapi_test_class_and_jars

The first one will deduce most defaults from the test name, but
still allows to optionally override most settings.

If a test doesn't match the default at all, the 2nd define still
shares the common jar files and the main Java UNO class, so the
second define adds these to your makefile.

The real fix is to add juh.jar to gb_JunitTest_use_jars.

Change-Id: I4342fdac5e31f85ea18fb4268e13c287a7adc2b7
Reviewed-on: https://gerrit.libreoffice.org/63118
Tested-by: Jenkins
Reviewed-by: Jan-Marek Glogowski <glogow@fbihome.de>
Move to MPLv2 license headers, with ESC decision and author's permission. 2013-04-22T08:37:38+00:00 Michael Meeks michael.meeks@suse.com 2013-04-19T20:10:42+00:00 62badf38283ef31e50d40e62f5d8bc3824c615d7 






gbuild: register all jars
2012-08-17T10:52:25+00:00

Michael Stahl
mstahl@redhat.com

2012-08-17T09:02:49+00:00

5a4bcd3b7578523af6a2754369231ca1cf413f82

Change-Id: I9f49970e5e06d1afd3fc066a20d1671c93e262fc





Change-Id: I9f49970e5e06d1afd3fc066a20d1671c93e262fc







gbuild: "use" vs. "add":
2012-04-07T23:05:52+00:00

Michael Stahl
mstahl@redhat.com

2012-04-07T21:22:08+00:00

c923f7d2c210dc7846767fc0ac6ece2a0d7812a8

Naming convention for gbuild methods:
- "add" is used for stuff that is logically a part of the target
  (i.e. not registered at the Module, but defined in the target's makefile)
- "use" is used for stuff that is logically a different target
  (i.e. it is registered at the Module, has it's own makefile, may be
  in a different module than the target)





Naming convention for gbuild methods:
- "add" is used for stuff that is logically a part of the target
  (i.e. not registered at the Module, but defined in the target's makefile)
- "use" is used for stuff that is logically a different target
  (i.e. it is registered at the Module, has it's own makefile, may be
  in a different module than the target)







gb_JunitTest_JunitTest takes only one argument
2012-02-20T15:39:59+00:00

Stephan Bergmann
sbergman@redhat.com

2012-02-20T15:39:59+00:00

fe981519f57a621c94e339a5453d7714af081acb