Hi Juan Pablo, My suspicion is still related to there being two Lucene engines in the mix.
If JSPWiki and Tika use *different* versions of Lucene there will be two Lucenes the classpath, and I've personally had all sorts of issues with Lucene instantiating when two components both use it (I seem to remember the "Version" can't be resolved, or something like that). Put it this way: I've noted that two Lucene engines in the same project might not like each other too much. I think I might have even had problems if they use the same version number there can be contention. So when I heard something in Tika related to Lucene was popping an NPE it set off my Lucene Alarm... But I've got some time this week so I'll be trying out the latest release, hopefully in the next few days. Cheers, Murray On 6/05/19 8:42 AM, Juan Pablo Santos Rodríguez wrote:
Hi Murray, thanks for looking into it :-) My findings so far: Lucene index related test are already in the main build, so that part should be covered, and regarding the Tika-related ones, they don't interact with Lucene, they only parse a couple of files, and check the extracted information (which is afterwards sent to Lucene, but that's outside the scope of the test). I was suspecting of something weird on the node in which the build kept running and made a new Jenkins job to do some tests (and avoid spamming dev@j.a.o) at https://builds.apache.org/job/jspwiki-test/ [...]
........................................................................... Murray Altheim <murray18 at altheim dot com> = = === http://www.altheim.com/murray/ === === = = === In the evening The rice leaves in the garden Rustle in the autumn wind That blows through my reed hut. -- Minamoto no Tsunenobu
