[
https://issues.apache.org/jira/browse/JCR-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259917#comment-13259917
]
Charles Erwin commented on JCR-3287:
------------------------------------
That could be the case, I have not changed my repository.xml for 2.4 from what
it was in 2.2. What was the exclusions excerpt that Jukka posted in the work
log of JCR-2885? Is that part of the indexing_configuration for Lucene? I
have not specified any additional indexing configuration, so it is using
whatever the default is.
I can create a few runnable Groovy files but setting up a Unit test might be
tough as the indexing is asynchronous and as such I'd have to throw in some
arbitrary wait period before attempting to see if the file has been indexed.
> Fulltext search breaking between 2.2 and 2.4.1
> ----------------------------------------------
>
> Key: JCR-3287
> URL: https://issues.apache.org/jira/browse/JCR-3287
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.4
> Environment: 11.3.0 Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41
> PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64 x86_64
> java version "1.6.0_29"
> Java(TM) SE Runtime Environment (build 1.6.0_29-b11-402-11D50b)
> Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02-402, mixed mode)
> Reporter: Charles Erwin
>
> Upgraded Jackrabbit Dependencies from 2.2.0 to 2.4.1 and now cannot get Full
> Text search to work. I have created a Github project to show the
> repository.xml configuration and the search code to prevent it being
> cluttered up here: https://github.com/greymeister/jackrabbit-2.4-search-bug
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
