On 08/05/18 16:55, ajs6f wrote:
Forking a thread off to dev@:
Do we have a global policy about where null is accepted as a wildcard? I know
it works in at least some places...
I would love to (over an appropriate period of time and with lots of warnings
and deprecation and so forth) stop
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/415
---
[
https://issues.apache.org/jira/browse/JENA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1543.
-
Resolution: Done
> Remote execution of JSON queries
>
>
>
[
https://issues.apache.org/jira/browse/JENA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468897#comment-16468897
]
ASF subversion and git services commented on JENA-1543:
---
Commit
[
https://issues.apache.org/jira/browse/JENA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468896#comment-16468896
]
ASF subversion and git services commented on JENA-1543:
---
Commit
[
https://issues.apache.org/jira/browse/JENA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468899#comment-16468899
]
ASF GitHub Bot commented on JENA-1543:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468898#comment-16468898
]
ASF subversion and git services commented on JENA-632:
--
Commit
On 08/05/18 16:55, ajs6f wrote:
Do we have a global policy about where null is accepted as a wildcard? I know
it works in at least some places...
> I know it works in at least some places...
Some operations are matches (Graph.find, Graph.contains, Graph.remove;
DatasetGraph similarly)
GitHub user hartig opened a pull request:
https://github.com/apache/jena/pull/418
pass a custom NodeFormatter to TurtleShell
â¦
added another constructor that can be used to
You can merge this pull request into a Git repository by running:
$ git pull
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
> That does not work because the `ParserProfileStd` supplied to
`TurtleStarReaderRIOT` has already been created, which is why the suggestion is
to use a forwarding proxy object (the wrapper) with
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
Add the PR #418
---
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/418
This PR provides the extension proposed in
https://github.com/apache/jena/pull/299#issuecomment-386918751
---
An upgrade to Ubuntu 18.04 forces java to openjdk 11 (the LTS, and 10.04
is an LTS as well).
Except it's not really Java 11! , which isn't due out until September,
it's java 10.0.1.
Surefire needs updating to 2.21.0 otherwise there is an NPE.
So, I've update the dependency in the top POM
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/419
JENA-1546: Cleanup for JDK10
* surefire update to 2.21.0 to avoid an NPE.
* Fixes in jena-iri for generated files; javadoc caused the build to stop
on [ERROR].
* Some cleaning of javadoc to
[
https://issues.apache.org/jira/browse/JENA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1546:
Description:
JDK10 javadoc production is needs some javadoc cleaned-up (jena-iri).
It also more
[
https://issues.apache.org/jira/browse/JENA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469558#comment-16469558
]
ASF GitHub Bot commented on JENA-1546:
--
GitHub user afs opened a pull request:
Andy Seaborne created JENA-1546:
---
Summary: Javadoc leaning for a build running using JDK10
Key: JENA-1546
URL: https://issues.apache.org/jira/browse/JENA-1546
Project: Apache Jena
Issue Type:
[
https://issues.apache.org/jira/browse/JENA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1546:
Summary: Javadoc fixing for a build running using JDK10 (was: Javadoc
leaning for a build running
18 matches
Mail list logo
