[jira] [Commented] (JENA-532) SecuredFunction leaves stack elements behind

2013-09-09 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/JENA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762415#comment-13762415 ] Hudson commented on JENA-532: - ABORTED: Integrated in Jena_Development_Test #933 (See [https://

[jira] [Resolved] (JENA-532) SecuredFunction leaves stack elements behind

2013-09-09 Thread Claude Warren (JIRA)
[ https://issues.apache.org/jira/browse/JENA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claude Warren resolved JENA-532. Resolution: Fixed Assignee: Claude Warren Resolved as per commit comments > Se

huge number of rules for a few RDF statements ?

2013-09-09 Thread chan
Hi, I'm considering the Jena Rules as a rule-based programming model where rules are being discovered and accumulated to grow tens of thousand, while the fact for inferring new info is only a few RDF statements. In this case, the rule engine may have to check each and every rule for the fact to f

[jira] [Commented] (JENA-532) SecuredFunction leaves stack elements behind

2013-09-09 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/JENA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762374#comment-13762374 ] ASF subversion and git services commented on JENA-532: -- Commit 1521302

[jira] [Created] (JENA-532) SecuredFunction leaves stack elements behind

2013-09-09 Thread Claude Warren (JIRA)
Claude Warren created JENA-532: -- Summary: SecuredFunction leaves stack elements behind Key: JENA-532 URL: https://issues.apache.org/jira/browse/JENA-532 Project: Apache Jena Issue Type: Bug

Re: Build and prep for 2.11.0

2013-09-09 Thread Andy Seaborne
I have (I hope!) fixed the logging in tests. The Fuseki test support code was manipulating the logging directly so that whether logging messages appeared could depend if the test class ran before or after firing up a background Fuseki test server. Also, there was a stray log4j.properties in t

[jira] [Created] (JENA-531) Remove code control of logging and use test log4j setup

2013-09-09 Thread Andy Seaborne (JIRA)
Andy Seaborne created JENA-531: -- Summary: Remove code control of logging and use test log4j setup Key: JENA-531 URL: https://issues.apache.org/jira/browse/JENA-531 Project: Apache Jena Issue Typ

AUTO: Mario Briggs is out of the office returning Sep 10th (returning 09/10/2013)

2013-09-09 Thread Mario Ds Briggs
I am out of the office until 09/10/2013. Note: This is an automated response to your message "Re: [jena-spatial] release preparation" sent on 09/09/2013 14:32:50. This is the only notification you will receive while this person is away.

JenaDriver (documentation - not critical)

2013-09-09 Thread Andy Seaborne
Rob, I came across this in org.apache.jena.jdbc.JenaDriver javadoc: * All Jena JDBC drivers are expected to have connection URLs which start with * the following: * * * * jena:jdbc:foo: * * * The {@code jena:jdbc:} portion is the common prefix for all Jena JDBC * drivers, the {@c

jena-security - WARNs in build

2013-09-09 Thread Andy Seaborne
Claude, In sorting out the whole build, I've been sorting out the logging during running the tests. jena-security was running the tests with no log4j configuration, and so getting: log4j:WARN No appenders could be found for logger (org.apache.jena.riot.stream.JenaIOEnvironment). log4j:WAR

Re: [jena-spatial] release preparation

2013-09-09 Thread Andy Seaborne
On 08/09/13 06:13, Ying Jiang wrote: Hi Andy, I can understand why to comment embedded Solr out. I've checked that all of your changes are acceptable. I've also moved the created files to target/... The code has been committed just now. Best regards, Ying Jiang Ying, Thanks - there may be a