Is Unitils project alive?

anybody knows whether unitils project is still alive. On there pages last version is 3.3 in maven repository it is 3.4.2.(Actually there is google cached version of their pages where the version is said to be 3.4.2)

Anyway is there any replacement for this project. I kind of lack the vivid community around and really don't want to be bound to dying project.

Solution

Unitils seems to be almost abandoned nowadays. Project is available on the GitHub here and you can look at its history and activity.

Anyways my two cents...

Unitils has serious drawbacks:

Integrates many third-party libs (easymock, dbunit, spring, dbmaintainer, xmlunit, slf4j etc) and thus forces their versions - it is a really serious drawback
Due to being dependent on many 3rd party libraries, it is almost impossible to keep it up to date without any company behind.
Unitils 4.0 is developed since 06.2011 and was planned to release at 01.2012, but now (01.2016) after 4 years is still not released.

DbUnit

For database-driven apps it may seem that interesting way to go is a plain DbUnit + Spring-Test or alternatively some 3rd party tools:

excilys/spring-dbunit that comes with handy @DataSet annotation and is actively developed on the github, also is constantly updated to use the newest versions of DbUnit and Spring Framework.
springtestdbunit/spring-test-dbunit which is also hosted on the github (comes with a @DatabaseSetup annotation).

Both are very similar, but personally I find DbUnit confusing, quite cumbersome and time-consuming. Why? Try to maintain large amount of small xml files and you find out what I mean. Also combining multiple data sets is really hard.

DbSetup

DbSetup may seem like a tempting proposition, but I also do not recommend it at all due to many drawbacks, like no compile time type checking (Insert.values() accepts Object), it does not allow arbitrary SQL execution (only inserts and deletes are permitted), using this library leads to a not readable code.

UPDATE 2023: sorry, but TBH these days, when dealing with setting up a relational database I prefer to create test fixtures as close as possible to the test case + using the source code itself. Optionally with database foreign key constraints disabled (if it makes sense). Alternatively loading the tiniest possible DB dump from SQL file is also an option - but without any weird 3rd party tools like dbunit/dbsetup/whatsoever.

Hope it helps.