summaryrefslogtreecommitdiff
path: root/unotest/Jar_test.mk
AgeCommit message (Collapse)AuthorFilesLines
2013-10-25stop looking for Jar files in solverMichael Stahl1-3/+3
Change-Id: I4d2a93fa7395354fbf2893df9e254ab39fa365af
2013-04-30Move to MPLv2 license headers, with ESC decision and author's permission.Michael Meeks1-21/+4
2012-09-05Java cleanup, remove unused classNoel Grandin1-1/+0
Change-Id: I27403fabc3b5326108a34655ffe8b2b0846c0694
2012-08-17gbuild: register all jarsMichael Stahl1-4/+4
Change-Id: I9f49970e5e06d1afd3fc066a20d1671c93e262fc
2012-08-15gbuild: remove most uses of gb_Jar_set_jarclasspath:Michael Stahl1-1/+1
With gb_Jar_add_jar and gb_Jar_add_system_jar adding to the manifest classpath automatically it is no longer necessary to call gb_Jar_set_jarclasspath manually except for the URE jars, which are apparently not supposed to be added automatically. Change-Id: I1e743e7ecb9cb5651e02005aa09e127bea1b0a29
2012-04-08gbuild: "use" vs. "add":Michael Stahl1-2/+2
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-10unotest: convert to gbuildMatúš Kukan1-0/+58