more documentation;
authorwenzelm
Fri, 22 Jul 2022 16:41:15 +0200
changeset 75689 29eb44a65a55
parent 75688 598994a2d339
child 75690 fc4eaa10ec77
more documentation;
src/Doc/Isar_Ref/Spec.thy
--- a/src/Doc/Isar_Ref/Spec.thy	Fri Jul 22 16:14:51 2022 +0200
+++ b/src/Doc/Isar_Ref/Spec.thy	Fri Jul 22 16:41:15 2022 +0200
@@ -1320,6 +1320,16 @@
   browsed via the virtual file-system with prefix ``\<^verbatim>\<open>isabelle-export:\<close>''
   (using the regular file-browser).
 
+  \<^descr> \<^theory_text>\<open>scala_build_generated_files paths (in thy)\<close> retrieves named generated
+  files as for \<^theory_text>\<open>export_generated_files\<close> and writes them into a temporary
+  directory, which is taken as starting point for build process of
+  Isabelle/Scala/Java modules (see @{cite "isabelle-system"}). The
+  corresponding @{path build.props} file is expected directly in the toplevel
+  directory, instead of @{path "etc/build.props"} for Isabelle system
+  components. These properties need to specify sources, resources, services
+  etc. as usual. The resulting \<^verbatim>\<open>jar\<close> module becomes an export artifact of the
+  session database.
+
   \<^descr> \<^theory_text>\<open>compile_generated_files paths (in thy) where compile_body\<close> retrieves
   named generated files as for \<^theory_text>\<open>export_generated_files\<close> and writes them into
   a temporary directory, such that the \<open>compile_body\<close> may operate on them as