You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add CI workflow that runs post-Mavenization CLI commands as described by docs/build.md
* Fix paths and other typos for out-of-source build instructions
* Rename Java system property UNICODETOOLS_OUTPUT_DIR to UNICODETOOLS_GEN_DIR and update vals in docs and CI that preserves dir structure
* Update Unicode version to 15.0.0 in new CI build workflow file
* Remove the `output` segment from Generated file paths for out-of-source builds
##### Notes for both out-of-source and in-source build workspaces
74
74
75
-
Currently, some tests run on the generated output files of a tool (ex: in order to test the validity of the output files). However, after converting these tests into standard JUnit tests, these unit tests are then run in isolation by default. Until we amend the code for such tests, those tests will fail by default. These tests are picked up and run by `mvn test`, and thus, by any other subsequent Maven target in the Maven lifecycle (ex: `package`, `install`).
76
-
77
-
For people who need `mvn test` or other subsequent Maven targets to succeed, a temporary workaround would be the following (which points the generated files directory to find the test input files from the repository sources):
cd <unicodetools-repo-root>; ln -s unicodetools/data/security output/Generated/security
86
-
```
87
-
88
-
This step to create a symbolic link on the file system is not necessary to run individual tools in Unicode Tools, nor is it intended to last long-term as we refactor code to establish stronger invariants and tests.
75
+
Currently, some tests run on the generated output files of a tool (ex: in order to test the validity of the output files). After converting these tests into standard JUnit tests, these unit tests are then run in isolation by default. Our code has been updated to support this behavior because it [now checks](https://github.com/unicode-org/unicodetools/commit/aa6d11c57fe8bbd20484d3a36123c8948e363262) for generated files in the `Generated` directory, and falls back to the repository's checked-in version when a command does not invoke the generation of a new version.
89
76
90
77
#### Java System properties used in Unicode Tools
91
78
92
79
(Note: The following example values for Java system properties are paths to local working copies that are organized using the out-of-source build workspace layout, as described above.)
0 commit comments