I think the clone projects warning is spurious. I had a quick look at
the source, and it appears to be a generic warning that just comes up
automatically if you don't specify a cloneProjectsTo directory. I
think we can safely ignore it.
Ian
On Tue, Nov 26, 2013 at 4:46 AM, Hudson (JIRA)
[
https://issues.apache.org/jira/browse/JENA-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Dickinson closed JENA-596.
--
Schemagen does not work with Maven 3.1.x
Key:
[
https://issues.apache.org/jira/browse/JENA-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Dickinson resolved JENA-596.
Resolution: Fixed
Fix Version/s: Jena 2.11.1
Schemagen does not work with Maven 3.1.x
Scott Patterson created JENA-597:
Summary: IRIResolverNormal needs thread safe CacheLRU
Key: JENA-597
URL: https://issues.apache.org/jira/browse/JENA-597
Project: Apache Jena
Issue Type: Bug
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Patterson updated JENA-597:
-
Environment: Any IBM JRE 7 or higher (was: Any IBM JRE 6 or higher)
IRIResolverNormal needs
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Patterson updated JENA-597:
-
Affects Version/s: (was: Jena 2.10.1)
Jena 2.11.0
IRIResolverNormal
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Patterson updated JENA-597:
-
Fix Version/s: (was: Jena 2.11.0)
IRIResolverNormal needs thread safe CacheLRU
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Patterson updated JENA-597:
-
Description:
The following exception may occur when more than one thread requires access to
the
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Patterson updated JENA-597:
-
Attachment: IRIResolverTest.java
IRIResolverNormal needs thread safe CacheLRU
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832914#comment-13832914
]
Andy Seaborne commented on JENA-597:
The fix to JENA-467 should fix the situation.
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832914#comment-13832914
]
Andy Seaborne edited comment on JENA-597 at 11/26/13 7:23 PM:
--
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-597:
---
Assignee: (was: Andy Seaborne)
IRIResolverNormal needs thread safe CacheLRU
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Patterson updated JENA-597:
-
Description:
The following exception may occur when more than one thread requires access to
the
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-597:
---
Comment: was deleted
(was: The fix to JENA-467 should fix the situation.
The stacktrace line
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Patterson updated JENA-597:
-
Environment: IBM Websphere 8 JRE (was: Any IBM JRE 7 or higher)
IRIResolverNormal needs thread
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832928#comment-13832928
]
Scott Patterson commented on JENA-597:
--
I opened this defect by cloned issue 467, which
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832926#comment-13832926
]
Andy Seaborne commented on JENA-597:
{{IRIResolver$IRIResolverNormal.init}}:
{noformat}
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832944#comment-13832944
]
Simon Helsen commented on JENA-597:
---
this stack trace matches 2.11. There are other calls
Hi,
Can anybody explain to me how does Jena map node to nodeId? The following is
stated in http://jena.apache.org/documentation/tdb/architecture.html
The Node to NodeId mapping is based on hash of the Node (a 128 bit MD5 hash -
the length was found not to major performance factor).
The
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832962#comment-13832962
]
Scott Patterson commented on JENA-597:
--
With the attached test, the trace is
Exception
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832987#comment-13832987
]
Andy Seaborne commented on JENA-597:
Static {{resolveIRI(String)}} need protecting.
[
https://issues.apache.org/jira/browse/JENA-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13833005#comment-13833005
]
Andy Seaborne edited comment on JENA-420 at 11/26/13 8:23 PM:
--
On 26/11/13 19:47, Yi Liao wrote:
Hi,
Hi there,
Can anybody explain to me how does Jena map node to nodeId? The
following is stated in
http://jena.apache.org/documentation/tdb/architecture.html
The Node to NodeId mapping is based on hash of the Node (a 128 bit
MD5 hash - the length was
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-597:
---
Attachment: JENA-597-1.patch
IRIResolverNormal needs thread safe CacheLRU
[
https://issues.apache.org/jira/browse/JENA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13833027#comment-13833027
]
Andy Seaborne commented on JENA-597:
Please try the attached patch (I don't have an IBM
25 matches
Mail list logo
