nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Solr Integration: why do we bring Lucene 2.4.1 in the solr home libs?

pl_componize

I'm working around Solr in Alfresco. I've sucessfully followed the docs to set up my Solr running, but I was wondering:

The solr war (patched or unpatched) contains Lucene 2.9.3 already. However in the solr zip provided by Alfresco, you can see that the lib folder of the solr home contains the Lucene 2.4.1 jars.

I guess it may be because some other alfresco jars might have been compiled against 2.4.1 (alfresco-integratino-xxx.jar or alfresco-data-model-xxx.jar) but I'm not sure.

So my question is why bring two versions of Lucene ?

I'm working with Enterprise 4.1.3

Find more posts tagged with

Comments

pl_componize

I'm still puzzled by the

alfresco-solr-integration‍

jar and

alfresco-solr‍

zip artifacts.

The Solr official release notes says 2.9.3. Why the dependencies of

alfresco-solr-integration‍

artifacts all points to 2.4.1?