Packaging: Java and XQuery code

[ChristianGruen]

Our current packaging mechanism detects either XQuery modules or Java archives. In many cases, the entry points of a Java archive are defined via an XQuery module, and it would be nice if both of them could be packaged and installed.

Idea (built on top of http://docs.basex.org/wiki/Repository#Java):

• In a JAR, the main class is defined in the MANIFEST.MF file:

Manifest-Version: 1.0
Main-Class: org.basex.modules.Hello

• If a .xqm file with this name exists additionally to the .class file in the installed JAR file, it will be extracted and used as the entry point:

 META-INF/
   MANIFEST.MF
 org/basex/modules/
   Hello.class
   Hello.xqm

• After installation, both Hello.jar and Hello.xqm will be in the repository. If the module is imported, the .xqm file takes precedence:

import module namespace m = 'http://basex.org/modules/Hello';
m:hello("Universe")

• The JAR file still needs to be imported from the XQuery module in the repository. This can be enforced by using the java: prefix:

(:~ Hello.xqm :)
module namespace m = 'http://basex.org/modules/Hello';

(: Import JAR file :)
import module namespace jar = 'java:org.basex.modules.Hello';

(:~
 : Creates a greetings strings.
 : @param  $guy  guy to greet.
 : @return greetings
 :)
declare function m:hello($guy as xs:string) as xs:string {
  jar:hello($guy)
};

Todos:

• REPO INSTALL: Extract .xqm file
• REPO DELETE: Delete both .jar and .xqm files

[ChristianGruen]

Documentation: http://docs.basex.org/wiki/Repository#Combined