diff --git a/build.sbt b/build.sbt index 0884fb3ea21..c40ef652fe3 100644 --- a/build.sbt +++ b/build.sbt @@ -296,6 +296,7 @@ lazy val enso = (project in file(".")) `connected-lock-manager`, syntax, testkit, + `common-polyglot-core-utils`, `std-base`, `std-database`, `std-google-api`, diff --git a/lib/scala/common-polyglot-core-utils/src/main/java/org/enso/polyglot/common_utils/package-info.java b/lib/scala/common-polyglot-core-utils/src/main/java/org/enso/polyglot/common_utils/package-info.java index eb2931c1703..409a398b72e 100644 --- a/lib/scala/common-polyglot-core-utils/src/main/java/org/enso/polyglot/common_utils/package-info.java +++ b/lib/scala/common-polyglot-core-utils/src/main/java/org/enso/polyglot/common_utils/package-info.java @@ -1,20 +1,22 @@ /** - * This package contains common utilities which can be used both by the engine runtime and the libraries. - *

- * This allows us to avoid duplicating code between the runtime and library projects for operations that need to be - * accessible on both sides. - *

- * The utilities that belong here are mostly operations that are builtins of the Enso language but also need to be used - * from our Java libraries where the cost of calling back to Enso methods is relatively high, so accessing the Java - * implementations directly is desirable. The primary example of that is the algorithm for computing the length of a - * string by counting the grapheme clusters. - *

- * Due to classpath separation, the class files of this package will be duplicated with one copy embedded in the engine - * and another attached as `common-polyglot-core-utils.jar` placed in the `polyglot` directory of the Standard.Base - * library. But it allows us to avoid duplicating the code, so we can have a single source of truth for each - * implementation. - *

- * Due to the copying, the project should not be expanded too much, but all utilities which would end up being - * duplicated are best moved here. + * This package contains common utilities which can be used both by the engine runtime and the + * libraries. + * + *

This allows us to avoid duplicating code between the runtime and library projects for + * operations that need to be accessible on both sides. + * + *

The utilities that belong here are mostly operations that are builtins of the Enso language + * but also need to be used from our Java libraries where the cost of calling back to Enso methods + * is relatively high, so accessing the Java implementations directly is desirable. The primary + * example of that is the algorithm for computing the length of a string by counting the grapheme + * clusters. + * + *

Due to classpath separation, the class files of this package will be duplicated with one copy + * embedded in the engine and another attached as `common-polyglot-core-utils.jar` placed in the + * `polyglot` directory of the Standard.Base library. But it allows us to avoid duplicating the + * code, so we can have a single source of truth for each implementation. + * + *

Due to the copying, the project should not be expanded too much, but all utilities which would + * end up being duplicated are best moved here. */ package org.enso.polyglot.common_utils;