Re: Documentation / Client access / Use from Java

Also had a look, and couldn't find where it is supposed to link. Nothing clear after looking at subversion as well. However, looking at Fuseki 1 documentation, I think that portion of the docs was not migrated to Fuseki 2. http://jena.apache.org/documentation/serving_data/#use-from-java

Re: How to edit Documentation ?

The CMS is very based on SVN, so you need to click the Update button for the equivalent of "svn update" of your working directory. It might be you have to climb one folder up within CMS before updating. On 7 Nov 2016 9:25 pm, "Claude Warren" wrote: > I tried using a private

Re: How to edit Documentation ?

On 07/11/16 21:25, Claude Warren wrote: I tried using a private browsing window in Firefox -- no change. :( On Mon, Nov 7, 2016 at 9:07 PM, A. Soroka wrote: You may be having the problems that I have repeatedly had with browser caching. An alternative move is to check

Re: How to edit Documentation ?

Hm. Have you tried changing your CMS-side working copy at: https://cms.apache.org/jena/ ? You can try "Force New jena Working Copy". --- A. Soroka The University of Virginia Library > On Nov 7, 2016, at 4:25 PM, Claude Warren wrote: > > I tried using a private browsing

Re: How to edit Documentation ?

I tried using a private browsing window in Firefox -- no change. :( On Mon, Nov 7, 2016 at 9:07 PM, A. Soroka wrote: > You may be having the problems that I have repeatedly had with browser > caching. An alternative move is to check out the SVN of the site from > >

Re: How to edit Documentation ?

You may be having the problems that I have repeatedly had with browser caching. An alternative move is to check out the SVN of the site from https://svn.apache.org/repos/asf/jena/site/trunk and edit it directly. You won't get the preview without setting up your own tooling, which is annoying.

How to edit Documentation ?

I know I have asked this before and even gotten good answers, but I can't seem to find the old messages so How do I get a copy of http://jena.apache.org/documentation/ that I can edit. The "improve this page" link does not seem to work for me. I get very old stuff. Claude -- I like:

Documentation / Client access / Use from Java

on http://jena.apache.org/documentation/fuseki2/ Client access -> Use from Java links to http://jena.apache.org/documentation/fuseki2/#sparql-java-clients But that does not exist. I would fix but I don't know where it is supposed to link. Claude -- I like: Like Like - The likeliest place on

Re: [] Release Apache jena 3.1.1 (2nd)

+1 Was able to build with -DskipTests for elephas. Ubuntu 16.04 (kernel 4.4.0-45) OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-2ubuntu0.16.04.2-b14) Claude On Mon, Nov 7, 2016 at 4:29 PM, Andy Seaborne wrote: > > > On 07/11/16 16:17, Stian Soiland-Reyes wrote: > >

TransformFilterImplicitJoin

Rob, I ran into some issue with TransformFilterImplicitJoin 1/ As noted in the javadoc, the join condition can not be between literals for the FILTER(?x = ?y) variant. While the javadoc for the control symbol says "This optimization is conservative - it does not take place if there is a

Re: [] Release Apache jena 3.1.1 (2nd)

On 07/11/16 16:17, Stian Soiland-Reyes wrote: I don't have much time to try out Jena while it's under development, as building Jena takes a very long time, We have addressed this in several ways: No need to build - Jena builds development maven artifacts every day or so. This is the

Re: [VOTE] Release Apache jena 3.1.1 (2nd)

As one of the people who was responsible for the HTTP Commons -based changes, I agree with Dave here. I should have a chance to do test builds sometime this evening. --- A. Soroka The University of Virginia Library > On Nov 7, 2016, at 11:22 AM, Dave Reynolds wrote:

Re: [VOTE] Release Apache jena 3.1.1 (2nd)

+1 > + does everything work on Linux? Build passed on Ubunbu 16.04, OpenJDK 1.8. > + are the GPG signatures fine? Validated with new key correctly. > + are the checksums correct? Yes. > + is there a source archive? Yes. > + can the source archive really be built? Yes, clean build from

Re: [] Release Apache jena 3.1.1 (2nd)

My apologies for finding this so late. As you will know, Commons RDF has just recently moved into preparing a release candidate that includes Jena support, which I originally had prepared using Jena 3.1.0. As that RC was dropped for other reasons, I thought I could have a go at using the next Jena

Re: [] Release Apache jena 3.1.1 (2nd)

At some point there just has to be a 3.1.1. Jena's release cycle is already too slow. -- Paul Houle paul.ho...@ontology2.com On Mon, Nov 7, 2016, at 08:56 AM, Andy Seaborne wrote: > > On 07/11/16 00:05, Stian Soiland-Reyes wrote: > > I'm afraid my vote is: > > > > -1 (non-binding) > > > >

[jira] [Commented] (JENA-1258) Context key is null (ARQConstants.registryFunctions) via NodeFmtLib

[ https://issues.apache.org/jira/browse/JENA-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644264#comment-15644264 ] ASF GitHub Bot commented on JENA-1258: -- Github user afs commented on the issue:

[GitHub] jena issue #189: JENA-1258 NodeFmtLib calls JenaSystem initializer

Github user afs commented on the issue: https://github.com/apache/jena/pull/189 The root cause: Commit 204f253 switched Context to using a `ConcurrentHashMap`, commit d67a426 added a check for null otherwise nothing has changed since 3.1.0. --- If your project is set up for

Re: [] Release Apache jena 3.1.1 (2nd)

On 07/11/16 00:05, Stian Soiland-Reyes wrote: I'm afraid my vote is: -1 (non-binding) because of broken initializers and confusing LICENSE in source archive. - repository JARs/POMs; broken initializers? IMO A single problem is not grounds for redoing a release. Just look at JIRA.

Re: [VOTE] Release Apache jena 3.1.1 (2nd)

+1 Built successfully on Linux. The Elephas I/O build takes about 60% of the total build time. -Osma On 05/11/16 00:43, Andy Seaborne wrote: Hi, Here is a vote on a release of Jena 3.1.1 (with Fuseki 2.4.1 and Fuseki 1.4.1). This is the second proposed candidate for this release. ** My

Re: [] Release Apache jena 3.1.1 (2nd)

I am unable to build due to Elephas issue. Probably due to underpowered build system. Perhaps we should figure out what the minimum build system needs to be. I'll try this evening without running elephas tests. +0 Claude On Mon, Nov 7, 2016 at 9:50 AM, Andy Seaborne wrote:

[jira] [Commented] (JENA-1258) Context key is null (ARQConstants.registryFunctions) via NodeFmtLib

[ https://issues.apache.org/jira/browse/JENA-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15643707#comment-15643707 ] ASF GitHub Bot commented on JENA-1258: -- Github user stain commented on the issue:

[GitHub] jena issue #189: JENA-1258 NodeFmtLib calls JenaSystem initializer

Github user stain commented on the issue: https://github.com/apache/jena/pull/189 Except for `impl` packages and suffixes it is never easy for Jena users to know what is "internal code". If it's in

Re: [] Release Apache jena 3.1.1 (2nd)

Please remove the VOTE label or use a separate thread for non-vote emails about the release. It makes finding actual votes a lot easier. Andy

[jira] [Commented] (JENA-1258) Context key is null (ARQConstants.registryFunctions) via NodeFmtLib

[ https://issues.apache.org/jira/browse/JENA-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15643652#comment-15643652 ] ASF GitHub Bot commented on JENA-1258: -- Github user afs commented on the issue:

[GitHub] jena issue #189: JENA-1258 NodeFmtLib calls JenaSystem initializer

Github user afs commented on the issue: https://github.com/apache/jena/pull/189 This usage is calling into the middle of internal code. Fixing output code seems wrong. It is better to initialize as objects get created, not on output. This shows the root cause is somewhere