On 14/10/13 09:11, Rob Vesse wrote:
Andy
Thanks for the great overview, I've been looking at supporting this on
dotNetRDF as well lately so have been thinking much along the same lines.
I think the check language first needs to be emphasized in messaging to
users about this change, dotNetRDF
[
https://issues.apache.org/jira/browse/JENA-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794146#comment-13794146
]
Andy Seaborne commented on JENA-555:
The call to {{QC.setFactory}} in
Andy Seaborne created JENA-564:
--
Summary: JSON parse errors blocks later use of JSON parser
Key: JENA-564
URL: https://issues.apache.org/jira/browse/JENA-564
Project: Apache Jena
Issue Type:
[
https://issues.apache.org/jira/browse/JENA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794171#comment-13794171
]
ASF subversion and git services commented on JENA-564:
--
Commit 1531932
[
https://issues.apache.org/jira/browse/JENA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-564.
--
JSON parse errors blocks later use of JSON parser
-
[
https://issues.apache.org/jira/browse/JENA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-564.
Resolution: Fixed
JSON parse errors blocks later use of JSON parser
[
https://issues.apache.org/jira/browse/JENA-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794181#comment-13794181
]
Hudson commented on JENA-564:
-
SUCCESS: Integrated in Jena_Development_Test #1000 (See
