Done - thanks.
Andy
On 12/12/2018 13:45, Anonymous CMS User wrote:
Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Flibrary-function.mdtext
Index:
Github user afs commented on the issue:
https://github.com/apache/jena/pull/473
@hartig - see PR #507 ; that should allow you to
`ResultSetWriterRegistry.register(SPARQLResultSetText, )` to
set your own text output engine.
For grabbing the prologue, see:
I only released Apache Commons components. Would Jena be too different/complex?
I have GitHub 2FA, ASF gpg keys (4096), Maven settings.xml set up for ASF maven
repo. So if the process is not too hard for a beginner, I can volunteer to
either sidekick and review/learn the process, or to RM
Coming back from a recess, so I think issues like these are easier for me to
help with - and I did something similar before.
It shouldn't be too complicated, but not sure if we can use Jekyll. As far as I
know, GitHub pages runs Ruby + Jekyll for every commit to the GitHub pages
branch.
We did the migration in Apache OpenNLP, moving also from the Apache CMS to a
Java based alternative to Ruby Jekyll.
But for Jena I think the easiest now would be to move everything to gitbox, and
then use gitpubsub instead of svnpubsub to publish the site.
Cheers
Bruno
+1
And I should have time for OSS development again from now until Feb next year.
So happy to help.
Thanks
Bruno
From: Andy Seaborne
To: "dev@jena.apache.org"
Sent: Thursday, 13 December 2018 7:19 AM
Subject: [VOTE] Move the code repo to gitbox.apache.org
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/506
---
[
https://issues.apache.org/jira/browse/JENA-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719305#comment-16719305
]
ASF GitHub Bot commented on JENA-1648:
--
GitHub user afs opened a pull request:
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/507
JENA-1648: First class text format for result sets.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/afs/jena text-format
Alternatively you can
+1 Approve the move
ajs6f
> On Dec 12, 2018, at 1:21 PM, Chris Tomlinson
> wrote:
>
> +1 To move code repo from git-wip-us to gitbox as soon as possible
>
> Chris
>
>> On Dec 12, 2018, at 12:17 PM, Andy Seaborne wrote:
>>
>> As per: email:
>>
Andy Seaborne created JENA-1648:
---
Summary: Make the result set text format a first-class
ResultSetLang for output.
Key: JENA-1648
URL: https://issues.apache.org/jira/browse/JENA-1648
Project: Apache
+1
On 12/12/2018 18:18, Andy Seaborne wrote:
(with deadline)
As per: email:
https://lists.apache.org/thread.html/5762798313a642dc90076e3562c83457571d92758d0d73e6010af0d0@%3Cdev.jena.apache.org%3E
this is a vote to move the code repo from git-wip-us.apache.org to the
gitbox.apache.org
On 12/12/2018 15:53, Chris Tomlinson wrote:
Hi Andy,
On Dec 12, 2018, at 7:35 AM, Andy Seaborne wrote:
On 11/12/2018 17:19, Chris Tomlinson wrote:
Hi Andy,
My GH and ASF accounts are linked. As I understand the note from D.Gruno once
jena is moved to GB then we can use either GB or GH
I'd like to move the site.
On 12/12/2018 15:25, ajs6f wrote:
I'm all in favor, and in favor of moving the site to git at the same time.
Indeed, we've discussed that latter before, but done nothing.
Bruno-- I think you had some thoughts about the site question? I seem to
remember that you did
+1 To move code repo from git-wip-us to gitbox as soon as possible
Chris
> On Dec 12, 2018, at 12:17 PM, Andy Seaborne wrote:
>
> As per: email:
> https://lists.apache.org/thread.html/5762798313a642dc90076e3562c83457571d92758d0d73e6010af0d0@%3Cdev.jena.apache.org%3E
>
> this is a vote to move
(with deadline)
As per: email:
https://lists.apache.org/thread.html/5762798313a642dc90076e3562c83457571d92758d0d73e6010af0d0@%3Cdev.jena.apache.org%3E
this is a vote to move the code repo from git-wip-us.apache.org to the
gitbox.apache.org service, which includes direct write access on github.
As per: email:
https://lists.apache.org/thread.html/5762798313a642dc90076e3562c83457571d92758d0d73e6010af0d0@%3Cdev.jena.apache.org%3E
this is a vote to move the code repo from git-wip-us.apache.org to the
gitbox.apache.org service, which includes direct write access on github.
If the vote
Hi Andy,
> On Dec 12, 2018, at 7:35 AM, Andy Seaborne wrote:
>
>
>
> On 11/12/2018 17:19, Chris Tomlinson wrote:
>> Hi Andy,
>> My GH and ASF accounts are linked. As I understand the note from D.Gruno
>> once jena is moved to GB then we can use either GB or GH or both in our
>> individual
I'm all in favor, and in favor of moving the site to git at the same time.
Indeed, we've discussed that latter before, but done nothing.
Bruno-- I think you had some thoughts about the site question? I seem to
remember that you did such a migration with another Apache project?
ajs6f
> On Dec
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/506
Cleanup of comments and javadoc. Trivial fixes.
Remove one "abstract" in an interface.
Correct QueryExecUtils handling of RDF-format result sets.
You can merge this pull request into a Git repository
Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Flibrary-function.mdtext
Index: trunk/content/documentation/query/library-function.mdtext
===
On 11/12/2018 17:19, Chris Tomlinson wrote:
Hi Andy,
My GH and ASF accounts are linked. As I understand the note from D.Gruno once
jena is moved to GB then we can use either GB or GH or both in our individual
workflows. For me just working with GH would be my choice.
I’m not sure how far
Github user afs commented on the issue:
https://github.com/apache/jena/pull/473
Jena is already extensible for results formats. See
`ResultSetWriterRegistry` and `ResultSetReaderRegistry`. I'm sorry there is old
code around but, well, time ... .
Adding
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/473
> Where and how are you wanting to output text format?
Where? In the command line tool for executing SPARQL* queries (see
[`ExecuteSPARQLStar` in
24 matches
Mail list logo
