Old internal notes?

2018-06-28 Thread ajs6f
Hey, Jena-folks, I found this page: https://jena.apache.org/documentation/notes/jena-internals.html while looking for something else, and after reading it, I wonder if it's a good thing to keep in the public documentation. It seems more than a bit out-of-date, since it refers to types that

[jira] [Commented] (JENA-1568) Don't use JUnit3 TestCase for in SSE tests

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526441#comment-16526441 ] Andy Seaborne commented on JENA-1568: - Look for "extends TestCase". There are only a few left. The

Re: [jira] [Commented] (JENA-1568) Don't use JUnit3 TestCase for in SSE tests

2018-06-28 Thread ajs6f
I'm not surprised. We do some clever things in tests! My suggestion is really just to add a ticket (an "epic" or whatever) to track overall migration status, so that we do at least have it on the table as a conscious long-term goal. ajs6f > On Jun 28, 2018, at 11:08 AM, Claude Warren wrote: >

Re: [jira] [Commented] (JENA-1568) Don't use JUnit3 TestCase for in SSE tests

2018-06-28 Thread Claude Warren
I remember munging around in Junit3 -> Junit4 conversion. It was not at all pretty. There are some constructs we use that do not map easily (dynamicly generated test suites comes to mind). But I agree we should migrate. On Thu, Jun 28, 2018 at 3:11 PM, A. Soroka (JIRA) wrote: > > [

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Claude Warren (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526383#comment-16526383 ] Claude Warren commented on JENA-1567: - Upon further investigation this looks like a but in

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526363#comment-16526363 ] Andy Seaborne commented on JENA-1567: - {noformat} com.sun.xml.internal.stream.XMLInputFactoryImpl true

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526347#comment-16526347 ] Andy Seaborne commented on JENA-1567: - Works for me - I also added lines to print the parsed model

[jira] [Commented] (JENA-1568) Don't use JUnit3 TestCase for in SSE tests

2018-06-28 Thread A. Soroka (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526333#comment-16526333 ] A. Soroka commented on JENA-1568: - [~andy.seaborne], is this an example of a larger program of migration

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Claude Warren (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526326#comment-16526326 ] Claude Warren commented on JENA-1567: - adding:       XMLInputFactory fac =

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Claude Warren (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526317#comment-16526317 ] Claude Warren commented on JENA-1567: - I get: 14:46:39.861 [main] ERROR org.apache.jena.riot -

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526238#comment-16526238 ] Andy Seaborne commented on JENA-1567: - See test case {{trix-10.trix}} where {{datatype=}} is

[jira] [Commented] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread Lee Kitching (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526236#comment-16526236 ] Lee Kitching commented on JENA-1566: Hi Rob,   Thanks for this, I've just tried 3.9.0-SNAPSHOT and

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526226#comment-16526226 ] Andy Seaborne commented on JENA-1567: - For the handling of xsd:string : JENA-1569 > Trix

[jira] [Created] (JENA-1569) Update StreamWriterTriX to handle xsd:string in RDF1.1 style.

2018-06-28 Thread Andy Seaborne (JIRA)
Andy Seaborne created JENA-1569: --- Summary: Update StreamWriterTriX to handle xsd:string in RDF1.1 style. Key: JENA-1569 URL: https://issues.apache.org/jira/browse/JENA-1569 Project: Apache Jena

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526219#comment-16526219 ] Andy Seaborne commented on JENA-1567: - What observable effect does this have? The example "Y" runs for

[jira] [Comment Edited] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526188#comment-16526188 ] Andy Seaborne edited comment on JENA-1567 at 6/28/18 11:20 AM: --- The issue is

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Claude Warren (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526188#comment-16526188 ] Claude Warren commented on JENA-1567: - The issue is in the XML parser.

[jira] [Updated] (JENA-1568) Don't use JUnit3 TestCase for in SSE tests

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-1568: Summary: Don't use JUnit3 TestCase for in SSE tests (was: Don't use Junti3 TestCase for in SSE

[jira] [Created] (JENA-1568) Don't use Junti3 TestCase for in SSE tests

2018-06-28 Thread Andy Seaborne (JIRA)
Andy Seaborne created JENA-1568: --- Summary: Don't use Junti3 TestCase for in SSE tests Key: JENA-1568 URL: https://issues.apache.org/jira/browse/JENA-1568 Project: Apache Jena Issue Type:

[jira] [Comment Edited] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526145#comment-16526145 ] Andy Seaborne edited comment on JENA-1567 at 6/28/18 9:17 AM: -- I don't see a

[jira] [Commented] (JENA-1567) Trix deserialization does not respect default namepace

2018-06-28 Thread Andy Seaborne (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526145#comment-16526145 ] Andy Seaborne commented on JENA-1567: - I don't see a problem. Try creating an integer, print out

[jira] [Updated] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread Rob Vesse (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Vesse updated JENA-1566: Affects Version/s: Jena 3.8.0 > Unable to parse VALUES clause containing boolean literal bindings >

[jira] [Updated] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread Rob Vesse (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Vesse updated JENA-1566: Fix Version/s: Jena 3.9.0 > Unable to parse VALUES clause containing boolean literal bindings >

[jira] [Resolved] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread Rob Vesse (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Vesse resolved JENA-1566. - Resolution: Fixed Resolved in development snapshots, if you can test 3.9.0-SNAPSHOT to verify that it

[GitHub] jena pull request #441: Improved Travis Configuration

2018-06-28 Thread rvesse
GitHub user rvesse opened a pull request: https://github.com/apache/jena/pull/441 Improved Travis Configuration - Skips Travis install phase - Test on both Oracle and Open JDK - Build full profile - Fix environment specification You can merge this pull request into a

[jira] [Commented] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526108#comment-16526108 ] ASF subversion and git services commented on JENA-1566: --- Commit

[jira] [Commented] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526107#comment-16526107 ] ASF subversion and git services commented on JENA-1566: --- Commit

[jira] [Commented] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526109#comment-16526109 ] ASF GitHub Bot commented on JENA-1566: -- Github user asfgit closed the pull request at:

[jira] [Commented] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526103#comment-16526103 ] ASF subversion and git services commented on JENA-1566: --- Commit

[jira] [Commented] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526104#comment-16526104 ] ASF subversion and git services commented on JENA-1566: --- Commit

[jira] [Commented] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526105#comment-16526105 ] ASF subversion and git services commented on JENA-1566: --- Commit

[jira] [Commented] (JENA-1566) Unable to parse VALUES clause containing boolean literal bindings

2018-06-28 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/JENA-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16526106#comment-16526106 ] ASF subversion and git services commented on JENA-1566: --- Commit

[GitHub] jena pull request #440: Fix SSE parsing on table with boolean values (JENA-1...

2018-06-28 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/440 ---