On a fresh AEM 6.5 SP4. Whenever I install either a new AEM archetype
project or the WKND starter project, AEM (or Sightly most likely) seem
to unregister, and only come back once the OSGi Bundle is fully Active.
Is a brief 4-10 seconds outage I get the image belowThere is also a long
stack trace but this is what it says02.06.2020 01:09:53.093 *ERROR*
[172.19.0.1  GET /sites.html/content HTTP/1.1]
Original error null...
Hi,How can I overlay/modify the filter options for the asset browser
(the side bar for authoring on every page). The Images option has a
pathfield but the Content Fragment option doesn't. Would I need to do
something additional to support the field being picked for filtering as
well?How do I add it?
Thanks for the reply, and yeah I guess I could do that for nowAs to the
actual issue, does it mean someone needs to do a fix in the uberjar
lucene version being used, or is AEM 6.5 using the wrong version?
Hey all, daycare sent me this wayI'm updating our current code that uses
uberjar 6.3.2 to use uberjar 6.5 and I found that some classes around
org.apache.lucene were reporting with compile errors.A particular one we
use is org.apache.lucene.analysis.standard.StandardAnalyzer, and while
my code compiles after changing the code, my components can't initialize
in AEM 6.5 due to the following:java.lang.NoSuchMethodError:
org.apache.lucene.analysis.standard.StandardAnalyzer: method ()V not