I did get it working, but I never checked it in, because I had to roll back from lucene 3 to lucene2 and change lots of stuff. This is because I had to use the compass library(which was only built with lucene 2 and has done dormant), which has a clustered database index. This allows multiple servers in a load balanced environments to see new posts on all servers. There is a catch, because the performance is a lot slower. I think the real solution is to run a separate apache solr server, and add support for forum search and posting to make calls to the solr server to add them to the index - that will be the most scalable solution.

It appears it's not finding your database settings. I don't have the exact 2.2.0 source so it's roughly in that area my guess. Make sure your jforum-custom.conf is setup properly and you're using the new SystemGlobals config file. The old one is missing lots of stuff the new one has. I would recommend starting with the new one and work backwards from there.

I did get the JDBC directory working, and it seems to work quite well BUT there is a major catch:
It needs compass 2.2.0, which is only lucene 2.4.1 compatible. It will not work with lucene 3.3.0.

On my local copy I have jforum rolled back to lucene 2.4.1 with the JDBC directory functioning well.
Another gotcha:
I had to disable the RAMWriter directory. Apparently there is a way to make this work, but I don't quite understand how the RamWriter is used with the 'batchCreate' method and how the flushing to the disk is currently working.

According to this post, there is a way to combine the two:

http://kalanir.blogspot.com/2008/06/loading-index-to-ram-and-flushing.html

But she is doing the 'copy' function, and I -think- jforum is using the index merging, but I'm not sure. I currently added a system global flag to turn it on and off.

Some other catches right now:
1) requires mysql or oracle (only tested on mysql)
2) requires a JNDI datasource. Everything else was a PITA. There might be away around this, but lucene jdbc really wants a datasource in the end anyways

Obviously I'm not checking this in, because I doubt anyways is excited to roll back to lucene 2.4.1. If someone can build compass with Lucene 3.3.0, the problem would be solved (It has seemed Compass has become dormant?)

I may try this first, as I think I can get this running for clustered environments quicker than a Solr integration:

http://kalanir.blogspot.com/2008/06/creating-search-index-in-database.html

If that route sucks I'll try messing with Solr. I've gotten everything working pretty well with Terracotta, the lucene reindex issue is the last big issue to tackle before it's solid I think. I'm not trilled with the mods to the *Repository files, but eventually I'd rather have it call the DAO layer directly (per item instead of reloading all of the items) if an item is not in the cache. That however presents some issues, like the other day when the Banlist saving was going in an infinite loop!

Hi, I am trying to get the lucene index to write to a NFS mount, however, it seems to hang the app. If I switch back to local filesystem it works. The problem I have, is in a multi server clustered environment, the indexes get off, and if you round robin a user between servers, the search results are inconsistent.

Anyone else run into this? It seems we can't set many options, except the analzyer it uses, but not the filesystem class. Also looking at the code, it seems if you turn off lucene searching, you don't get any search at all?

Another question - how often does it reindex, does it run a quartz job, and can we set how often it polls if we do? Or do I need to add that?

I've gotten this combo working. However you need to patch all of the XXXRepository.java classes, because they crash if a key is missing out of the cache, instead of reloading it. I also have the POM too which is sort of the missing link. I submitted it to the Andowson if he wants to apply it to the source or not. Let me know if anyone else needs it.

We're using the SecureSSO module (sort of meant for Grails, but I think it'll work for any java project). You might try that one:

http://blog.smartkey.co.uk/2009/10/secure-sso-for-jforum/

I did find a bug that I had to fix, it would get a NPE if the SSO cookie was not set and the user went directly to the forums - the source is included so you can add a null check for that to fix it - other than that it works for us.

nervermind, I just checked the requirements, and it said Maven 3. I installed maven 3, and now I can compile the project.

Hi, I am trying to build 2.3.1, but I keep running into this error:

generics are not supported in -source 1.3
(use -source 5 or higher to enable generics)
public List<ModerationLog> selectAll(final int startFrom, final int count)

I get similar error for all files that use generics.

I am running linux, with Sun JDK 1.60.24, maven 2.0.6

I miss the easy Ant build

I emailed with the same question, and Andowson said he added a tag for 2.3 source.

Thanks Andowson for picking up the torch on this project!