I have just merged in changes for a new maven module to hold the java for the distribution command line tools. This new module puts all the commands in one place. They retain their original java package names to limit changes for users.

Commands covered are those from jena-core, jena-arq, and jena-tdb - the ones in the binary distribution.

Fuseki2 also puts these commands in its server jar - people have found executing from just the server jar a convenient feature. This can be reconsidered; this change is not an opinion on that aspect.

The binary distribution (zip, tar.gz) now depends on module jena-cmds. tdbloader2 scripts are affected and updated (the one internal package change to separate the command from the machinery, which remains in jena-tdb).

Maven artifact apache-jena-libs does not depends on module jena-cmds so using that artifact will now miss the commands. Maven artifact apache-jena (as a <type>pom) should get them. That's the theory: A touch of caution here because my machine is now potentially contaminated by development artifacts.

        Andy

https://issues.apache.org/jira/browse/JENA-1108

Reply via email to