summaryrefslogtreecommitdiff
path: root/forms/JunitTest_forms_complex.mk
AgeCommit message (Collapse)AuthorFilesLines
2018-11-09Fix many Java subsequentcheck test by using JUHJan-Marek Glogowski1-7/+1
Splits gb_JunitTest_set_unoapi_test_class_and_jars into two separate defines as: - gb_JunitTest_use_unoapi_jars - gb_JunitTest_use_unoapi_test_class Then replaces many of the gb_JunitTest_use_jars lists with the new gb_JunitTest_use_unoapi_jars to fix the JUH dependencies. This probably adds some unneeded JUH dependencies to some Java tests, but that shouldn't be a problem. Change-Id: I0c4fce6b50f7c6eb8d62bfb2c50f056b97584794 Reviewed-on: https://gerrit.libreoffice.org/63119 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 Meeks1-23/+4
2012-08-17gbuild: register all jarsMichael Stahl1-5/+5
Change-Id: I9f49970e5e06d1afd3fc066a20d1671c93e262fc
2012-04-08gbuild: "use" vs. "add":Michael Stahl1-1/+1
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 Bergmann1-1/+1
2011-08-10prefer makefile-gmake-mode to plain makefile-modeTakeshi Abe1-1/+1
2011-07-30Add consistent Emacs and vim mode linesTor Lillqvist1-0/+1
2011-06-20gnumake4: fix buildbreakers from mergeBjoern Michaelsen1-1/+1
2011-03-28migrate forms subsequenttests to gbuildBjoern Michaelsen1-0/+46