[
https://issues.apache.org/jira/browse/JENA-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030402#comment-13030402
]
Andy Seaborne commented on JENA-62:
-----------------------------------
What is the migration plan for a separate LARQ module?
Can we try for a switch over at the next release? Having both internal and
external LARQ seems to
1/ The ARQ distribution contains the LARQ code and a copy of Lucene. Will the
user still be able to download and run just using the ARQ download? i.e is LARQ
to be packed into the ARQ zip file?
2/ Where will the documentation be?
3/ What about Lucene 2 -> Lucene 3? LUCENE-2675?
> Remove LARQ from ARQ
> --------------------
>
> Key: JENA-62
> URL: https://issues.apache.org/jira/browse/JENA-62
> Project: Jena
> Issue Type: Sub-task
> Components: ARQ, LARQ
> Reporter: Paolo Castagna
> Assignee: Paolo Castagna
>
> LARQ (as well as the Lucene dependency) needs to be removed from ARQ.
> ARQ will use the separate LARQ module.
> Since LARQ depends on Lucene and ARQ and we cannot have cycles in our
> dependency graph, ARQ cannot depend on LARQ.
> LARQ is a sort of plug-in for ARQ and we could load it and wire it in into
> ARQ if present in the classpath, in a similar way as showed here:
> http://markmail.org/thread/r5phyiuqkqsyi2xc
> Should we change the namespace for the property function?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
