Re: [basex-talk] Module versioning for new packaging system

For the most part, I'm glad to have the non-EXPath packaging mechanism introduced for 7.2.1 -- [...]

• No mechanism for atomically upgrading a module exists; it must be

uninstalled, then installed again, leaving an intermediate period in which the module is unavailable.

We could add a "force" flag to the "repo install" command; a "repo update" would be another alternative. Ideas?

• No mechanism for attaching a version to a module exists, making it

impossible to determine whether an upgrade is necessary.

..this won't happen before the release of 7.2.1 or 7.3, because we'd have to invest more time (than currently available) in a clean concept.

Everyone: I have just added some Annotations to the QueryModule; this way, the permissions of functions and other properties can be fine tuned, and Java code can thus be better optimized by the XQuery processor:

http://docs.basex.org/wiki/Java_Bindings#Context-Awareness