[GitHub] jena pull request: A maven module for Jena cmds

Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/118 --- 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 enable

[GitHub] jena pull request: A maven module for Jena cmds

Github user ajs6f commented on the pull request: https://github.com/apache/jena/pull/118#issuecomment-168724113 Right, that's why I said "re-appear". They appear in the original modules, and now in the new one. As I wrote, it's not anything to worry about and mostly just about my expe

[GitHub] jena pull request: A maven module for Jena cmds

Github user afs commented on the pull request: https://github.com/apache/jena/pull/118#issuecomment-168723921 (wrong button) --- 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 enabl

[GitHub] jena pull request: A maven module for Jena cmds

GitHub user afs reopened 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-td

[GitHub] jena pull request: A maven module for Jena cmds

Github user afs closed the pull request at: https://github.com/apache/jena/pull/118 --- 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 b

[GitHub] jena pull request: A maven module for Jena cmds

Github user afs commented on the pull request: https://github.com/apache/jena/pull/118#issuecomment-168723495 No package names have been invented. They are the same as before, just now in one module. --- If your project is set up for it, you can reply to this email and have your rep

[GitHub] jena pull request: A maven module for Jena cmds

Github user ajs6f commented on the pull request: https://github.com/apache/jena/pull/118#issuecomment-168719708 Okay. I found it odd that so many package names re-appear in the new artifact. I'm used to OSGi habits, but this is nothing to cavil at, just my predilections. --- If your

[GitHub] jena pull request: A maven module for Jena cmds

Github user afs commented on the pull request: https://github.com/apache/jena/pull/118#issuecomment-168711323 @ajs6f Some of the commands already have two names, one from jena.XYZ. It used a reflection call to call forward in the build chain; now the commands included have direct call

[GitHub] jena pull request: A maven module for Jena cmds

Github user rvesse commented on the pull request: https://github.com/apache/jena/pull/118#issuecomment-168709925 Looks like a good first step --- 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 t

[GitHub] jena pull request: A maven module for Jena cmds

Github user ajs6f commented on the pull request: https://github.com/apache/jena/pull/118#issuecomment-168695738 +1 to the general plan here, definitely. Is the future plan to migrate the namespaces as well? --- If your project is set up for it, you can reply to this email and have yo

[GitHub] jena pull request: A maven module for Jena cmds

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