Fuseki does not currently compile and some other things have changed
without warning in such a way a build would affect a user:
I would prefer that systems are always in a state whereby they can be
built and released unless they is good reason and notification.
1/ Depends on a non-existent TDB 0.8.11-SNAPSHOT
2/ Introduces a dependency on talis-oss-snapshots Maven repository.
3/ Updating the dependencies does not get a working development system.
It also uses LARQ and seems to force Lucene 3 - isn't that a one-way
migration isn't it?
Andy
On 09/05/11 11:11, Paolo Castagna (JIRA) wrote:
[
https://issues.apache.org/jira/browse/JENA-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Castagna updated JENA-63:
-------------------------------
Attachment: JENA-63_TDB_r8797.patch
JENA-63_ARQ_r8773.patch
Add LARQ to TBD and Fuseki
--------------------------
Key: JENA-63
URL: https://issues.apache.org/jira/browse/JENA-63
Project: Jena
Issue Type: Improvement
Components: Fuseki, LARQ, TDB
Reporter: Paolo Castagna
Assignee: Paolo Castagna
Attachments: JENA-63_ARQ_r8773.patch, JENA-63_TDB_r8797.patch,
TDB-r8763.patch
It is possible (although not easy for users) to use LARQ with TDB and Fuseki.
This is to make possible and easy to use LARQ with TDB datasets and with Fuseki.
One way to achieve this is to improve DatasetAssemblerTDB in TDB as suggested
by http://markmail.org/thread/r5phyiuqkqsyi2xc. This way, LARQ will be loaded
and wired into ARQ if present in the classpath. Uses will need just to add the
LARQ jar to their classpath (or depend on it if they use Maven).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
