I have released the 0.3.0a version of Contentment. This is an important release as security and the API has reached a very solid point. I do not believe there will be anymore rewrites of the core code anymore. There may be some slight modifications yet, but the API should be very stable from this point forward.
This is merely an upgrade to the 0.2.0x. Only one minor change has been made to the web.xml deployment descriptor that really isn't even worth mentioning. I can't believe it didn't need any code fixes for the tests to succeed!
This is a major API update. So far, it is untested, but I hope to get to that soon and make another release in a week or two as an alpha. This new system is very exciting and I hope that I can write some nice information about in on the project page in a couple weeks. For now, check out the changelog for details.
Well, the long overdue alpha release of the code is available. Someone might actually look at this thing now. It is being released as an Alpha instead of Beta because of the lack of functionality. I believe the code should actually be very stable.
While this is good news, this isn't very exciting. This is the first compiling release and I intend to update CVS on a daily basis now--that is, at the end of each day I'm working on it. This is untested and certainly doesn't do anything. The next release will probably be another 'x' release (experimental) and then I hope to have an 'a' release after that (alpha/partly tested).
Well, after much fighting with PHP, I've decided that Contentment is not suited for a PHP-based environment. It takes too long to interpret so many pages stacked together, the OO system is nasty, and I can't write for reuse very well--which is over half of what Contentment is supposed to let me do. Contentment will now be written in Java and have a new synonym: ContentmentJ. I'm already much farther along after a night than I was after a few weeks on the PHP version. Nothing against PHP, it just isn't well-suited for this task.