[jira] [Commented] (JENA-1704) Enable Apache Sonar reports
[ https://issues.apache.org/jira/browse/JENA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830142#comment-16830142 ] Andy Seaborne commented on JENA-1704: - I originally thought the reports are generated separately from the build - then it works for anyone using the build whether they have access to send results to Apache or not. This makes sense because there is a magic key for the reports in SonarCloud. But the mentions of POM changes suggests otherwise. Give it a go and we can see what happens. > Enable Apache Sonar reports > --- > > Key: JENA-1704 > URL: https://issues.apache.org/jira/browse/JENA-1704 > Project: Apache Jena > Issue Type: Improvement > Components: Build >Reporter: A. Soroka >Assignee: A. Soroka >Priority: Trivial > > Apache offers a Sonar service at [https://builds.apache.org/analysis.] We > should take advantage of it in a non-intrusive way. Enabling Sonar analysis > must not annoy anyone working on the codebase or make development less > pleasant, so it must be done carefully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (JENA-1644) ParameterizedSparqlString Empty List fix
[ https://issues.apache.org/jira/browse/JENA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne closed JENA-1644. --- > ParameterizedSparqlString Empty List fix > > > Key: JENA-1644 > URL: https://issues.apache.org/jira/browse/JENA-1644 > Project: Apache Jena > Issue Type: Bug >Affects Versions: Jena 3.9.0 >Reporter: Greg Albiston >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.11.0 > > > ParameterizedSparqlString throws a StringIndexOutOfBoundsException when empty > list of values is provided. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (JENA-57) Schemagen does not cope well with resources that have multiple language tags
[ https://issues.apache.org/jira/browse/JENA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne closed JENA-57. - > Schemagen does not cope well with resources that have multiple language tags > > > Key: JENA-57 > URL: https://issues.apache.org/jira/browse/JENA-57 > Project: Apache Jena > Issue Type: Bug > Components: Cmd line tools >Reporter: Ian Dickinson >Assignee: Bruno P. Kinoshita >Priority: Minor > > Schemagen does not generate very good comments when multiple rdfs:comment > triples are attached to a resource, denoting different localized comments. > There should be an option to set the preferred language(s), and only matching > comments included. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (JENA-1675) Simple typo
[ https://issues.apache.org/jira/browse/JENA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne closed JENA-1675. --- > Simple typo > --- > > Key: JENA-1675 > URL: https://issues.apache.org/jira/browse/JENA-1675 > Project: Apache Jena > Issue Type: Bug > Components: Documentation >Reporter: Kofi shango >Assignee: A. Soroka >Priority: Trivial > Labels: documentation, newbie > > On the page [https://jena.apache.org/tutorials/sparql_datasets.html] > There is a line "Datasets don't have to created just for the lifetime of the > query." > That should be "Datasets don't have to be created just for the lifetime of > the query." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (JENA-1687) Precise return types of NodeFactory methods
[ https://issues.apache.org/jira/browse/JENA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne closed JENA-1687. --- > Precise return types of NodeFactory methods > --- > > Key: JENA-1687 > URL: https://issues.apache.org/jira/browse/JENA-1687 > Project: Apache Jena > Issue Type: Improvement >Reporter: Jan Martin Keil >Assignee: Andy Seaborne >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > I propose to precise the return types of the NodeFactory methods, e.g. to set > NodeFactory#createURI return type to Node_URI. This makes the developers life > easier, as there is no longer a need to cast after creating a Node, if one > need a specific node type. I can not see any disadvantages and it should be > backward compatible (except of classes that override these methods). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (JENA-1069) Simpify the internal naming of the default graph (Quad constants)
[
https://issues.apache.org/jira/browse/JENA-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-1069.
---
> Simpify the internal naming of the default graph (Quad constants)
> -
>
> Key: JENA-1069
> URL: https://issues.apache.org/jira/browse/JENA-1069
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
>Affects Versions: Jena 3.0.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> There are two different constants for the default graph for what seemed at
> the time, slightly different situations. The idea was that quads from the
> default graph of a dataset would be {{Quad.defaultGraphIRI}} and quads
> created by parsers, would be {{Quad.defaultGraphNodeGenerated}}. The idea was
> that the output of the parser was "default graph" but it was being redirected
> into a named graph. This does not now seem useful.
> {{Quad.defaultGraphIRI}} = {{}}
> {{Quad.defaultGraphNodeGenerated}} = {{}}
> In SPARQL, the application is using {{GRAPH }}. Using
> {{}} wil not work consistently.
> The proposal is to combine these two as {{Quad.defaultGraphIRI}}, possible
> migrate to {{Quad.defaultGraph}}, or even a class or enum for the graph
> naming constants.
> These constants should never have been written to disk in database, certainly
> not {{}}, but just to make sure, the operation
> {{Quad.isDefaultGraph(Node)}} can take the old name into account for a
> release cycle.
> Nearly all the changes are in tests where the expected output has been
> explicitly written into test results.
> There is another, little used, constant -- {{Quad.tripleInQuad}} -- for when
> a triple is in a quad just to be transported around, meaning "meaningless",
> "unknown" or "doesn't matter". This would not change. It exists to be
> different from {{Quad.defaultGraphIRI}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (JENA-1689) Polyadic#m_subGraphs should be a Set
[ https://issues.apache.org/jira/browse/JENA-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne closed JENA-1689. --- > Polyadic#m_subGraphs should be a Set > > > Key: JENA-1689 > URL: https://issues.apache.org/jira/browse/JENA-1689 > Project: Apache Jena > Issue Type: Improvement >Reporter: Jan Martin Keil >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > I propose that Polyadic#m_subGraphs should be a Set, not a List, to avoid > duplicated addition of graph instances causing performance issues or > unexpected behavior in case of removal of a graph. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (JENA-1687) Precise return types of NodeFactory methods
[ https://issues.apache.org/jira/browse/JENA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1687. - Resolution: Won't Fix Assignee: Andy Seaborne > Precise return types of NodeFactory methods > --- > > Key: JENA-1687 > URL: https://issues.apache.org/jira/browse/JENA-1687 > Project: Apache Jena > Issue Type: Improvement >Reporter: Jan Martin Keil >Assignee: Andy Seaborne >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > I propose to precise the return types of the NodeFactory methods, e.g. to set > NodeFactory#createURI return type to Node_URI. This makes the developers life > easier, as there is no longer a need to cast after creating a Node, if one > need a specific node type. I can not see any disadvantages and it should be > backward compatible (except of classes that override these methods). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [jena] afs commented on issue #546: JENA-1687: refine NodeFactory return types
afs commented on issue #546: JENA-1687: refine NodeFactory return types URL: https://github.com/apache/jena/pull/546#issuecomment-487892216 Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jena] jmkeil commented on issue #546: JENA-1687: refine NodeFactory return types
jmkeil commented on issue #546: JENA-1687: refine NodeFactory return types URL: https://github.com/apache/jena/pull/546#issuecomment-487882901 Yes. The change is unnecessary. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jena] jmkeil closed pull request #546: JENA-1687: refine NodeFactory return types
jmkeil closed pull request #546: JENA-1687: refine NodeFactory return types URL: https://github.com/apache/jena/pull/546 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
Re: [RESULT] [VOTE] Apache Jena 3.11.0 RC2
Thanks for RM'ing Andy!! CheersBruno On Tuesday, 30 April 2019, 8:19:16 pm NZST, Andy Seaborne wrote: The vote passes with PMC +1 votes from Andy,Bruno and Aaron, and community +1 vote from Marco. Andy On 24/04/2019 11:53, Andy Seaborne wrote: > Hi, > > Here is a vote on a release of Apache Jena 3.11.0. > This is the second proposed release candidate. > > The deadline for the vote is Saturday, 27th April at 17:00 UTC
[jira] [Commented] (JENA-1572) Setup LICENSE and NOTICE files to reflect Jena's "release all" policy.
[ https://issues.apache.org/jira/browse/JENA-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830088#comment-16830088 ] ASF subversion and git services commented on JENA-1572: --- Commit 460774e4be5ec87d8b44d8573076f8ca8f1d42d5 in jena's branch refs/heads/master from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=460774e ] Merge pull request #561 from afs/license-notice JENA-1572: Remove L in modules that don't need them > Setup LICENSE and NOTICE files to reflect Jena's "release all" policy. > -- > > Key: JENA-1572 > URL: https://issues.apache.org/jira/browse/JENA-1572 > Project: Apache Jena > Issue Type: Improvement >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Priority: Major > Attachments: JenaLN.txt > > Time Spent: 20m > Remaining Estimate: 0h > > The LICENSE and NOTICE files can be tided up. They were setup so individual > modules can be released by themselves but Jena now releases all modules at > once. > See attached file for an assessment of the current (3.8.0) situation. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1572) Setup LICENSE and NOTICE files to reflect Jena's "release all" policy.
[ https://issues.apache.org/jira/browse/JENA-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830087#comment-16830087 ] ASF subversion and git services commented on JENA-1572: --- Commit 743e794c9519ef28defebe816a20b56919ea33d2 in jena's branch refs/heads/master from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=743e794 ] JENA-1572: Remove L in modules that don't need them > Setup LICENSE and NOTICE files to reflect Jena's "release all" policy. > -- > > Key: JENA-1572 > URL: https://issues.apache.org/jira/browse/JENA-1572 > Project: Apache Jena > Issue Type: Improvement >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Priority: Major > Attachments: JenaLN.txt > > Time Spent: 20m > Remaining Estimate: 0h > > The LICENSE and NOTICE files can be tided up. They were setup so individual > modules can be released by themselves but Jena now releases all modules at > once. > See attached file for an assessment of the current (3.8.0) situation. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [jena] afs merged pull request #561: JENA-1572: Remove L in modules that don't need them
afs merged pull request #561: JENA-1572: Remove L in modules that don't need them URL: https://github.com/apache/jena/pull/561 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jena] afs commented on issue #546: JENA-1687: refine NodeFactory return types
afs commented on issue #546: JENA-1687: refine NodeFactory return types URL: https://github.com/apache/jena/pull/546#issuecomment-487873750 Given the other PRs and discussion on [JENA-1687](https://issues.apache.org/jira/browse/JENA-1687), I don't think we should make the change from the top class (in effect, the interface) and the specific concrete implementations. Thank you to @jmkeil for suggesting it and making sure we do think about issues. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jena] afs edited a comment on issue #547: JENA-1688: add methods Node#asBlank, Node#asConcret, Node#asLiteral, Node#asURI, Node#asVariable
afs edited a comment on issue #547: JENA-1688: add methods Node#asBlank, Node#asConcret, Node#asLiteral, Node#asURI, Node#asVariable URL: https://github.com/apache/jena/pull/547#issuecomment-476405301 This seem related to PR#546 and the discussion on [JENA-1687](https://issues.apache.org/jira/browse/JENA-1687). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [jena] afs merged pull request #566: Update maven-bundle-plugin
afs merged pull request #566: Update maven-bundle-plugin URL: https://github.com/apache/jena/pull/566 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[RESULT] [VOTE] Apache Jena 3.11.0 RC2
The vote passes with PMC +1 votes from Andy,Bruno and Aaron, and community +1 vote from Marco. Andy On 24/04/2019 11:53, Andy Seaborne wrote: Hi, Here is a vote on a release of Apache Jena 3.11.0. This is the second proposed release candidate. The deadline for the vote is Saturday, 27th April at 17:00 UTC
