[
https://issues.apache.org/jira/browse/JENA-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502633#comment-14502633
]
Andy Seaborne commented on JENA-914:
Jena uses Xerces for more than just XML parsing.
[
https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502908#comment-14502908
]
ASF GitHub Bot commented on JENA-849:
-
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/38
---
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
[
https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14502907#comment-14502907
]
ASF subversion and git services commented on JENA-849:
--
Commit 99ca3fcd
[
https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-849.
--
Resolution: Fixed
Fix Version/s: Jena 2.13.1
> Incorrect version numbers in schemagen maven documen
The nice thing is that there are two (semi-)independent strands:
1/ Direct Junit3 -> Junit4 update
2/ Improving the quality of tests with contracts.
that means (2) can proceed at it's own natural pace.
Andy
On 20/04/15 07:28, Claude Warren wrote:
Here is the svn link to the earlier w
All of a sudden, I seeing m2e problems with the RAT plugin on several
machines. It's causing an Eclipse error "Plugin execution not covered
by lifecycle configuration".
I don't understand why this has started happening to me because I don't
see any changes that are relevant.
In an attempt t
PS
Not directly relevant to jena-core but I'm testing out a Junit4 runner
that parsers manifest files.
A lot of SPARQL testing is driven by RDF-based manifests, including the
material developed by the SPARQL working groups.
https://github.com/afs/mantis/tree/master/dboe-quack/src/test/java/
I think there is a manifest parser in the example code... .but again, I
would have to go looking for it.
On Mon, Apr 20, 2015 at 6:39 PM, Andy Seaborne wrote:
> PS
>
> Not directly relevant to jena-core but I'm testing out a Junit4 runner
> that parsers manifest files.
>
> A lot of SPARQL testin
I used to add information in the project pom, but some OSS projects didn't
allow adding IDE specific options in the project settings.
Now, after I import a Maven project into Eclipse, whenever I find messages like
this, I simply choose the Quick-Fix option "Mark goal $GOAL as ignored in
Eclipse
On 20/04/15 21:57, Bruno P. Kinoshita wrote:
I used to add information in the project pom, but some OSS projects didn't
allow adding IDE specific options in the project settings.
Now, after I import a Maven project into Eclipse, whenever I find messages like this, I
simply choose the Quick-Fi
Hi All,
Here is the test case (data in N-QUADS, two simple SPARQL queries, and a
test Java code) that my colleague Miriam constructed.
Both queries seem to return incorrect results. We have tried Jena 2.11.1
libraries, 2.12.1, and 2.13.
They all have the same behavior as far as this test case
[
https://issues.apache.org/jira/browse/JENA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504374#comment-14504374
]
ASF subversion and git services commented on JENA-380:
--
Commit 11d2d0e3
[
https://issues.apache.org/jira/browse/JENA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504381#comment-14504381
]
ASF subversion and git services commented on JENA-380:
--
Commit be0e6f27
[
https://issues.apache.org/jira/browse/JENA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504430#comment-14504430
]
ASF subversion and git services commented on JENA-380:
--
Commit e2f4d02d
15 matches
Mail list logo
