Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/77
---
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
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/77#issuecomment-113557412
Thank you. Code merged with some changes:
* Version was used elsewhere (jena-elephas) so I put it back.
* Didn't update rdfcat; the `BiConsumer` additions are only
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/77#issuecomment-112795366
Sorry, @afs, when you say Moving into jena-base is probably the best first
step. are you referring to `ArqCmdGeneral`/`CmdGeneral`?
---
If your project is set up for it,
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/77#issuecomment-112862578
Okay, I've got `ModVersion` out to `jena-base` and moved `Version` into it
as an inner class (since `ModVersion` is the only client of `Version`). We are
still doing the the
GitHub user ajs6f opened a pull request:
https://github.com/apache/jena/pull/77
Move arq.cmd.* to jena-base's jena.cmd
https://issues.apache.org/jira/browse/JENA-961
This is a multi-module PR, but I could find no other way to do it: since
several Jena modules depend on
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/77#issuecomment-112548845
Moving into jena-base is probably the best first step. It separates it
from gathering all the commands which may well not be good idea anyway, or at
least, a pointless