GitHub user afs opened a pull request:

    https://github.com/apache/jena/pull/118

    A maven module for Jena cmds

    This new module puts all the commands in one place.  They retain their 
original java package names.
    
    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 PR does not change that aspect.
    
    The binary distribution (zip, tar.gz) now depends on module jena-cmds.
    
    Maven artifact `apache-jena-libs` does not so using that artifact will now 
miss the commands.
    
    Maybe this module should be called apache-jena-cmds as a delivery unit.  Or 
maybe we should keep as is, and add apache-jena-cmds as a combined single jar 
for the main commands.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/afs/jena jena-cmds

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jena/pull/118.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #118
    
----
commit 9d94e4a8201b851dbfe875969c690457c2b2289f
Author: Andy Seaborne <[email protected]>
Date:   2016-01-02T21:28:04Z

    JENA-1108 : jena-cmds module

commit 2614e6121c43f63a40d37375d39211d456ff66e3
Author: Andy Seaborne <[email protected]>
Date:   2016-01-03T11:46:34Z

    JENA-1108: Command line tools for TDB bulkloader2

commit 16e232b727059c97901f65af0b3a0454da5e64bd
Author: Andy Seaborne <[email protected]>
Date:   2016-01-04T14:28:56Z

    Invoke utility
    
    Can be used to call commands in a later-in-build module

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to