summaryrefslogtreecommitdiff
path: root/ucb/JunitTest_ucb_unoapi.mk
AgeCommit message (Collapse)Author
2018-11-09Simplify and fix Java UNO API test makefilesJan-Marek Glogowski
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>
2013-04-22Move to MPLv2 license headers, with ESC decision and author's permission.Michael Meeks
2012-08-17gbuild: register all jarsMichael Stahl
Change-Id: I9f49970e5e06d1afd3fc066a20d1671c93e262fc
2012-04-08gbuild: "use" vs. "add":Michael Stahl
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)
2012-02-20gb_JunitTest_JunitTest takes only one argumentStephan Bergmann
2011-08-10prefer makefile-gmake-mode to plain makefile-modeTakeshi Abe
2011-07-30Add consistent Emacs and vim mode linesTor Lillqvist
2011-06-22gnumake4: adjust ucb to gbuildBjoern Michaelsen
2011-03-28migrate ucb subsequenttests to gbuildBjoern Michaelsen