[jira] [Commented] (JENA-632) Generate JSON from SPARQL directly.

[ https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277477#comment-14277477 ] Bruno P. Kinoshita commented on JENA-632: - Here's the list of what I think are the r

[jira] [Commented] (JENA-632) Generate JSON from SPARQL directly.

[ https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277458#comment-14277458 ] Bruno P. Kinoshita commented on JENA-632: - Hi! I have [updated the grammar|https:

[jira] [Comment Edited] (JENA-848) jena-text Lucene concurrency issues

[ https://issues.apache.org/jira/browse/JENA-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276912#comment-14276912 ] Andy Seaborne edited comment on JENA-848 at 1/14/15 1:46 PM: - I'

[jira] [Commented] (JENA-848) jena-text Lucene concurrency issues

[ https://issues.apache.org/jira/browse/JENA-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276912#comment-14276912 ] Andy Seaborne commented on JENA-848: I'm unclear from the description what happens if up

Re: git merges

Looking at your source tree I assume you're talking about the hadoop branch :) Generally speaking there's two modes of operations with git: A) Public mode You're pushing the code to a public repo like apache and you cannot rewrite the code (at least /should/ not) A lot of people would recommend

[jira] [Commented] (JENA-803) Custom aggregates in SPARQL.

[ https://issues.apache.org/jira/browse/JENA-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276882#comment-14276882 ] Andy Seaborne commented on JENA-803: Fix pushed (sorry - it didn't get tagged for the JI

Re: git merges

For branches that haven't diverged too much you can do a git rebase instead but that is more error prone and personally I dislike it because it essentially changes history and certainly you can't safely do it for branches that have been pushed remotely which is almost inevitable for longer lived fe

git merges

Fine tuning our processes ... Rob is now ahead with "[??/93]" :-) OK - he's sub-contracted the work of the actually commit to others. Is there anyway we can stop this? Is there a better way to merge two branches in git? Andy

[jira] [Commented] (JENA-849) Incorrect version numbers in schemagen maven documentation

[ https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276774#comment-14276774 ] Alexander Willner commented on JENA-849: Also, under "Specifying processing options"

[jira] [Commented] (JENA-849) Incorrect version numbers in schemagen maven documentation

[ https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276750#comment-14276750 ] Rob Vesse commented on JENA-849: We don't list the versions explicitly anywhere other than f

[jira] [Commented] (JENA-846) Add IRI.toUri

[ https://issues.apache.org/jira/browse/JENA-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276747#comment-14276747 ] ASF subversion and git services commented on JENA-846: -- Commit 2941cf75

[jira] [Commented] (JENA-847) There is a need for a generic assembler for SecurityEvaluators.

[ https://issues.apache.org/jira/browse/JENA-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276748#comment-14276748 ] ASF subversion and git services commented on JENA-847: -- Commit 72d29e63

[jira] [Commented] (JENA-849) Incorrect version numbers in schemagen maven documentation

[ https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276745#comment-14276745 ] Alexander Willner commented on JENA-849: And here is the original reporter. Thanks f

[jira] [Commented] (JENA-849) Incorrect version numbers in schemagen maven documentation

[ https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276739#comment-14276739 ] Ian Dickinson commented on JENA-849: Good point, Rob, thanks. The original reporter was

[jira] [Commented] (JENA-849) Incorrect version numbers in schemagen maven documentation

[ https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276734#comment-14276734 ] Rob Vesse commented on JENA-849: Ideally the documentation should not call out a specific ve

[jira] [Commented] (JENA-839) E_Regex only works with XSDstring.

[ https://issues.apache.org/jira/browse/JENA-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276700#comment-14276700 ] Andy Seaborne commented on JENA-839: Agreed. For reference the list is in the spec: [

[jira] [Updated] (JENA-849) Incorrect version numbers in schemagen maven documentation

[ https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Dickinson updated JENA-849: --- Description: Reported by Alexander Willner. Documentation for the Schemagen maven plugin has the wrong

[jira] [Created] (JENA-849) Incorrect version numbers in schemagen maven documentation

Ian Dickinson created JENA-849: -- Summary: Incorrect version numbers in schemagen maven documentation Key: JENA-849 URL: https://issues.apache.org/jira/browse/JENA-849 Project: Apache Jena Issue