| 1 | Each file in directory simple must follows hierarchy conventions and is compiled/jared
|
|---|
| 2 | automatically into server's working directory and content of resources likewise.
|
|---|
| 3 | The name of jnlp is independent, and there can be even more jnlps for each future jar.
|
|---|
| 4 | Directories are honored in srcs and in resources, but not in testcases.
|
|---|
| 5 | Directories in signed handle their content in similar way as simple's content is handled,
|
|---|
| 6 | but in addition final jars are signed with simple testkey.
|
|---|
| 7 | Files in custom directory have to care about compilation/packaging and deploying of srcs
|
|---|
| 8 | directory themselves. This can affect also testcase and resources, but testcases and
|
|---|
| 9 | resources are still automatically prepared like they are in the other test types.
|
|---|
| 10 | There are three reproducers â simpletest1, simpletest2 and deadlocktest, which tests
|
|---|
| 11 | testâs suite itself and serve as examples of behaviour.
|
|---|
| 12 |
|
|---|
| 13 | Directory "signed" is listed in Makefile.am. You can specify as much to-be-signed
|
|---|
| 14 | directories as you want. And jars in each of those signed directories will be
|
|---|
| 15 | signed by their's own unique key (number of signed directories == number of certificates).
|
|---|
| 16 | Do not forget to add each this directory into list n Makefile.am
|
|---|
| 17 |
|
|---|
| 18 | If the name of a folder in simple/signed is composed of dots, then its contents
|
|---|
| 19 | are deployed from under a directory structure such that each part evaluates to
|
|---|
| 20 | a folder. For example, my.dir.reproducer/ will be deployed as jnlp_test_server/my/dir/reproducer.jar.
|
|---|
| 21 |
|
|---|
| 22 | Inside custom directory are expected directories which are handling themselves.
|
|---|
| 23 | The only strictly necessary file is custom/reproducerName/srcs/Makefile. Upon
|
|---|
| 24 | all custom/*/srcs are then launched make prepare-reproducer and during cleaning make
|
|---|
| 25 | clean-reproducer. Those targets are run after all simple and signed reproducers are
|
|---|
| 26 | prepared, so they can reuse components of the simple and signed reproducers, eg
|
|---|
| 27 | certificates or dependencies. to keep this custom makefiles as simple as possible.
|
|---|
| 28 | Some comment in makefile or readme file is recommended for each custom reproducer
|
|---|
| 29 | to tell dependencies and what it does. Some readme (or comment in classes) is good
|
|---|
| 30 | advice for any reproducer anyway;)
|
|---|
| 31 | Because of automake only small set of variables from icedtea-web Makefile is
|
|---|
| 32 | available for custom makefiles, but feel free to export others if needed.
|
|---|
