[
https://issues.apache.org/jira/browse/JENA-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100655#comment-13100655
]
Paolo Castagna commented on JENA-63:
------------------------------------
What's stopping this going into Fuseki trunk is the fact that if we add a
dependency on LARQ to Fuseki, it will be on a SNAPSHOT (since LARQ has not been
released yet). So, this would forbid Fuseki to be released. JENA-62 is a
related issue but not a blocker for this, in my opinion.
I'd like to close this issue and add LARQ to Fuseki.
Perhaps, we could release LARQ as we used to do before Apache or use LARQ as a
test drive for the release process in Apache. Either option would do for me
(and it probably will not be all right the first time we do). My preference is
to test drive the Apache release process and do it on Apache infrastructure.
By the way, LARQ uses the maven-release-plugin to publish SNAPSHOTs, but I've
never tested to publish releases on the Apache Maven Repository. We use the
maven-release-plugin @ Talis with no particular problems (and it does automate
a lot of manual, boring and error prone steps (such as tagging, for example)).
> Add LARQ to TDB 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_Fuseki_r1136050.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
