Lucis upgraded to Lucene 3.5

Well, at last the jump was made, and based on the previous 2.9.x branch, the migration to Lucene 3.5 has been done with version 3.5.2 now available in central. Apart from the migration work, the most significant changes include:

• Writer configuration suppliers, to deal with the fact that certain Lucene objects, such as merge policies, can't be shared.
• Managed readers, not based on the new searcher manager, but integrated with the lucis store architecture.

A Lucis branch for Lucene 2.9.x

As a said in the previous entry, the upgrade to Lucene 3.x may take longer than expected, so to provide an evolution path, a branch based on Lucene 2.9.x has just been released (version 2.9.5, based on Lucene 2.9.4).

It is not a mere recompile. Use of deprecated methods has been removed and the new collectors has been put in use.

A Lucis update

After a too long period of inactivity at last we have a significant update to Lucis. The migration to Lucene 3.x has been put on hold to work on some more important changes (and I don't know if it will happen before the move to Lucis' successor project). So, to avoid confusion, version numbering has changed so that the first two numbers match those of the Lucene version used.

I have just released version 2.4.31 (should be in central soon), the main changes being:

• Reindexing indexes can now hold a checkpoint.
• Reindexing indexes can know decide to skip a run.
• Cancellation policy for index services has been defined, using interruptions, providing graceful shutdowns. As always for all your java concurrency-related questions, go to the source.
• It is know possible to use external executors.
• Many more tests.

Also, as of this version, the javadoc is no longer uploaded to the repository, as it can be built from source, but the relevant parts are online for your reading convenience.

UPDATE: Already in Central.

Stick to version 2.0 of Maven Release Plugin

As reflected on bugs MRELEASE-694 (related to MRELEASE-689 and MRELEASE-691), there are some problems generating the release version numbers (like maintaining SNAPSHOT). This may bite without notice if use non-interactive mode. These bugs are still open as of version 2.2.1.

It's a nice coincidence that because of another bug, the Maven Eclipse Plugin warns you if you use a Maven Release Plugin version other than 2.0 :)

Revisiting Lucis

The lucis project is a key component of an increasing number of web sites. However, it is starting to show its age. Rushed into production in the summer of 2008 it included some "incorrect" decisions that were to be mended in its successor project, which was also going to include all the important updates. So lucis algo received small evolutions.

However, as the first release of conquiris is delayed again and again, and the number fo projects using lucis increases far more than expected, it is clear that a new impulse was needed.

So today, I've released version 0.0.31 (which should be in Maven Central in a few hours). The only (but fundamental) change is the upgrade from Lucene 2.4.1 to 3.1.0. As the new Lucene version already breaks backwards compatibility, I've gone the whole way and removed use of (now) deprecated parts of Lucene. So this version of lucis is totally incompatible with the previous stable one (0.0.29).

I hope to post about the changes real soon now.

As I said, the "only" change is the Lucene version, so this release won't be integrated in Port@l and GeNews until more improvements are added.

New Look

Three years after the First Post, I've decided to give this blog a new look, maybe as a first step in posting more often.

So, I've turned to the Blogger Template Designer, chosen a clear and simple one, removed most ads, and converted code snippets to Gist.GitHub.

I hope you like it.

Great presentation for entrepeneurs

From Zero to a Million Users - Dropbox and Xobni lessons learned

View more presentations from Adam Smith

Gist.GitHub Gadget

Some months ago I wanted to embed some code snippets stored in Gist.GitHub in some Google Sites-based documentation, just to find that you cannot use the script tag directly. So, I decided to wrap the embedding code in a Google Gadget. You can find it here.