Github user stain commented on the issue:
https://github.com/apache/jena/pull/189
Yes, your pull request looks like the best approach.
On 8 Nov 2016 12:33 pm, "Andy Seaborne" <notificati...@github.com> wrote:
> The better fix is to initialize in NodeFactory (and Node for legacy
> reasons) only. I have tested this in a build.
>
> There is little point in a specific test because tests run in the overall
> suite; it's almost confusing to have a test that doesn't. With
> initialization in NodeFactory this will get tested anyway!
>
> Also, it would help to unroll ARQConstants (for RDF, RDFS, OWL, XSD) so it
> does not need JenaSystem.init and then it is, with care, init-safe.
>
> See PR#192 for that all made real.
>
> The original example works when run separately to ensure minimal system
> initialization.
>
> â
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/jena/pull/189#issuecomment-259124635>, or mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AAPd5fFN_RTsft_0zoh3lFvprRyNmYrsks5q8Gu3gaJpZM4Kqwha>
> .
>
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
