+
+
Enable tracing to start collecting statistics. Run
+- queries as usual (through any eXist interface), then press "Refresh" to see
++ queries as usual (through any interface), then press "Refresh" to see
+ statistics.
+
+
diff --git a/exist-distribution/src/xar-patches/monex/0002-remotes-html-wording.patch b/exist-distribution/src/xar-patches/monex/0002-remotes-html-wording.patch
new file mode 100644
index 0000000000..be0793fa2a
--- /dev/null
+++ b/exist-distribution/src/xar-patches/monex/0002-remotes-html-wording.patch
@@ -0,0 +1,29 @@
+--- /Users/lauretta/Documents/evolvedbinary/elemental/exist-distribution/target/expath-pkgs-monex-staging/remotes.html 2026-05-30 21:12:45
++++ /Users/lauretta/Documents/evolvedbinary/elemental/exist-distribution/target/expath-pkgs-monex-staging/remotes.html 2026-07-29 09:30:25
+@@ -61,7 +61,7 @@
+
+
+ Alert!
+- Remote monitoring requires eXist's scheduler
++ Remote monitoring requires the scheduler
+ module to be enabled. See extensions/build.properties and
+ conf.xml.
+
+@@ -76,7 +76,7 @@
+ responsiveness of the system.
Response Time is the elapsed time
+ until the client received the response.
+
Configuration
+-
To monitor remote eXist-db instances, edit the XML file instances.xml in the root collection of
++
To monitor remote instances, edit the XML file instances.xml in the root collection of
+ the monex application. Monex pings each server at configurable times or
+ intervals. You can also set up email alerts in notifications.xml.
+
The configuration for monitoring a remote instance looks as follows:
+@@ -121,7 +121,7 @@
+
token |
+
the unique JMX token required to connect to the JMX servlet. This token is generated
+ for every server and can be found in the file jmxservlet.token
+- inside the data directory of the eXist instance. Note: eXist versions before 2.2
++ inside the data directory of the instance. Note: eXist-db versions before 2.2
+ do not use this mechanism, so no token is required. |
+
+
diff --git a/exist-distribution/src/xar-patches/packageservice/0001-exist-compatible-version.patch b/exist-distribution/src/xar-patches/packageservice/0001-exist-compatible-version.patch
new file mode 100644
index 0000000000..6a818fed3f
--- /dev/null
+++ b/exist-distribution/src/xar-patches/packageservice/0001-exist-compatible-version.patch
@@ -0,0 +1,22 @@
+--- /Users/lauretta/Documents/existdb-packageservice/modules/packages.xqm 2022-02-16 14:33:52
++++ /Users/lauretta/Documents/evolvedbinary/elemental/exist-distribution/target/expath-pkgs-packageservice-staging/modules/packages.xqm 2026-07-22 13:17:43
+@@ -288,7 +288,7 @@
+ (: should be private but there seems to be a bug :)
+ declare function packages:public-repo-contents($installed as element(repo-app)*) {
+ try {
+- let $url := $config:DEFAULT-REPO || "/public/apps.xml?version=" || packages:get-version() ||
++ let $url := $config:DEFAULT-REPO || "/public/apps.xml?version=" || packages:get-existdb-compatible-version() ||
+ "&source=" || util:system-property("product-source")
+ (: EXPath client module does not work properly. No idea why. :)
+ let $request :=
+@@ -323,8 +323,8 @@
+ };
+
+ (: should be private but there seems to be a bug :)
+-declare function packages:get-version() {
+- (util:system-property("product-semver"), util:system-property("product-version"))[1]
++declare function packages:get-existdb-compatible-version() {
++ util:system-property("exist-db-expath-pkg-compatible-version")
+ };
+
+ (: should be private but there seems to be a bug :)