4 zip files containing ridl, unoloader, jurt and juh source files are
created and copied to solver and unzipped again in odk when odk could
simply run javadoc over the source files directly.
Change-Id: I8d2d7c794988eab2e8a3c6005cc8a849a1232f64
... because otherwise types that have been removed from the input rdb
still end up in the resulting jar file.
Change-Id: Ia73ecffcc9d831f2627ac0fcc5f57acf1f52a799
... derives from com.sun.star.uno.RuntimeException instead of
com.sun.star.uno.Exception.
Only test that breaks with this change is jurt_uno/AnyConverter_Test,
which for mysterious reasons effectively tests that
IllegalArgumentException is a subclass of Exception and not
RuntimeException. Presumably this is just a generic exception test that
happens to use IllegalArgumentException.
Some further testing indicates there are no problems expected at
runtime:
Running "make subsequentcheck" with all Java test code compiled against
a ridl.jar that does not contain the change, running against a soffice
that uses ridl.jar and rdbs with the change + ridl.jar with the change
on the test side yields exactly the same AnyConverter_Test failure, with
no other failures.
Change-Id: Iad183de76ec7e0d56648084e97cdcc160b5b033d
Apparently it is possible to lose updates there, or at least i've had a
failure where only 34 out of 35 increments were performed when checking
in passedAsyncTest from JobQueue_Test.testStaticThreadExecutesAsyncs.
Change-Id: I823ac65980e4e94be21305a10b98b4cfca247c81
This patch remove some '@author' for Java souce files, and removes some
commented code founded when removing the '@author'.
Change-Id: Ic4fcd028a9cdbd85c693d93bcd48e41f36386d22
Always link in gb_STDLIBS, except when the library explicitly opts out
with gb_LinkTarget_disable_standard_system_libs.
Change-Id: I489a99114fbfa46d0421a27cf6c7b899dc268a4a
Remove jurt/demo code, because it doesn't compile anymore, and according
to S.Bergmann, it doesn't test anything that isn't already tested
elsewhere.
Change-Id: I775eb1681d77800abc8f8d399c43de20d8721e82
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
this removes dmake completely out of the build for migrated modules
build.pl now assumes modules to be gbuild, unless there is a
prj/dmake file
Change-Id: I674a036b182ee13c5ec093e83cb3d38133112d3b
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)
