Age | Commit message (Collapse) | Author | |
---|---|---|---|
2012-08-17 | gbuild: register all jars | Michael Stahl | |
Change-Id: I9f49970e5e06d1afd3fc066a20d1671c93e262fc | |||
2012-04-08 | gbuild: "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-03-23 | fdo#46102: Fix Java script examples after gbuild'ification | Stephan Bergmann | |
...they contained no class files anymore, due to missing gb_Jar_set_packageroot calls. However, those calls only work for subdirectories, i.e., the example .java files need to be put into a package (I chose org.libreoffice.example.java_scripts) for all of them). This in turn required adaption of the parcel-descriptor.xml files; not sure what the logicalname entries there are good for if anything -- the macro names at "Tools - Macros - Run Macro..." now unfortunately(?) contain the fully qualified paths for the HelloWorld, HighlightText, and MemoryUpdate examples. There are additional examples at scripting/examples/java/ that apparently do not get packaged (but I adapted them anyway). | |||
2011-10-23 | no need for SRCDIR parameter here | Matúš Kukan | |
2011-10-01 | finished converting scripting to gbuild | Matúš Kukan | |