[GitHub] jena pull request #447: JENA-1574: Resolve named graph URIs.

[afs <gi...@git.apache.org>]

GitHub user afs opened a pull request:

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

    JENA-1574: Resolve named graph URIs.

    

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

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

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

    https://github.com/apache/jena/pull/447.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 #447
    
----
commit eef54c1109bbe7b6110618d609dc431e92238e5a
Author: Andy Seaborne <an...@...>
Date:   2018-07-12T11:01:59Z

    JENA-1574: Resolve named graph URIs.

----


---

[GitHub] jena issue #447: JENA-1574: Resolve named graph URIs.

[afs <gi...@git.apache.org>]

Github user afs commented on the issue:

    https://github.com/apache/jena/pull/447
  
    Yes - it is a bit tricky to do deep testing. This is partially offset by the fact the command line tools are ways to call the core functionality so are small. I think most commands can now run "in-JVM" and they don't call e.g. `System.exit` but I'm not sure how uniform this is.


---

[GitHub] jena issue #447: JENA-1574: Resolve named graph URIs.

[kinow <gi...@git.apache.org>]

Github user kinow commented on the issue:

    https://github.com/apache/jena/pull/447
  
    Code looks good, and I think this is for a recent e-mail thread in one of the mailing lists. Are you going to add any unit tests as well? Not sure if it's easy/doable to test that part as well. Otherwise will approve as-is.


---

[GitHub] jena pull request #447: JENA-1574: Resolve named graph URIs.

[asfgit <gi...@git.apache.org>]

Github user asfgit closed the pull request at:

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


---