Fix existdb function signatures

[line-o]

With the releases of exist-db 5.0.0, 5.1.0 and 5.3.0 some function signatures changed, some where deprecated or even removed and new ones added.

This PR attempts to update all of these modules

• xmldb
• util
• lucene

In addition this PR adds new processor versions 5.0, 5.1 and 5.3 (5.2 intentionally left out) and selects a new static XQuery context if version 5.0 or later is selected.

[line-o]

I also had a look at the list of module namespaces injected into the XQuery static context and found several ones that were removed in eXist 5+

declare namespace console = "http://exist-db.org/xquery/console";
declare namespace datetime = "http://exist-db.org/xquery/datetime";
declare namespace example = "http://exist-db.org/xquery/example";
declare namespace httpclient = "http://exist-db.org/xquery/httpclient";
declare namespace math-ext = "http://exist-db.org/xquery/math";

But I am unsure how to have separate contexts for different processor versions.

[CanOfBees]

Hi @line-o -

Apologies for the state of the eXist function signatures. I recall wanting to help @rhdunn with updates to the eXist functions but then getting confused trying to determine which functions had been changed after the update to 5.0. I didn't do a very good job exploring in-depth or asking the right questions.

As for getting different processor versions, there are some annotations for that, which can be found in the following annotations.xqy file. For a possible example, see some of them used in the BaseX modules; e.g. admin.xqy.

Hopefully that's helpful.
Best!

[line-o]

@CanOfBees Hi!
I puzzled together a possible solution to add a separate static context for existdb versions 5 and up. But this is my first time writing Kotlin so there is very likely a more elegant solution. :)

[duncdrum]

nice work you might want to update the readme to mention 5.3.0 as well

[line-o]

Stupid typo here :( xmldb:copy-*
QUESTION: Can the see-also annotation be used multiple times?

[rhdunn]

Yes, the see-also annotation can be used multiple times. Currently, these annotations are not used by my plugin. They are there when I do get that working. I have the data model in place, so I just need to query the annotations and add the corresponding inspection code that checks these annotations.

[rhdunn]

Merged. Thanks!