Initially, EmForge-0.33.1 was planned as small bug-fixing release, contained only critical bugs for one very important installation. But, finally (after about 1 month delay) it contains many bug-fixes and some very important improvements:

• Many big-fixes related to local-symbols support;
• Many bug-fixes and small improvement related to wiki and attachments;
• Speed improvement for displaying SCM History and ChangeLog pages;

Full list available on Milestone Closed Tasks page

Liferay Support#

One of the biggest feature, implemented in this release - we started to work on Liferay integration. Liferay - is a most popular, open-source portal solution and we already received many requests from users to make it possible use EmForge from Liferay Portal.

Some users (as I know), already implemented some own portlets, some other reported EmForge integrated into Liferay via IFRAME Portlet, but, our target is implement set of native Liferay portlets, provided all EmForge functionality and reused all Liferay features.

Current version is first (even small) step on this way - currently, only Source Control Management (SCM) functionality is available as portlet, but, we will continue work in this direction. Finally, I see EmForge 1.0 (then it will be done) as Liferay + EmForge Portlets + EmForge Theme - we result, we will able to reuse incredible set of features, provided by Liferay.

More information about portlet available at EmForge Liferay Portlets project.

Major Links:#

• EmForge-0.33.1 Milestone and closed tasks
• EmForge Liferay Portlets
• Download
• EmForge Quick Start
• EmForge Setup Guide
• EmForge Mail Lists
• EmForge Short Introduction

EmForge team is happy to announce new version of EmForge-0.33. Several changes done here:

Edit/Delete comments#

Now, it is possible to edit/delete comments for pages and tasks. This action is usually available for comment author, as well as for some "super-users": admin for whole site and project manager for tasks, related to specific project. It is possible to edit/delete only last comment (but admin can edit/delete ANY comments)

Better clustering support and environment tasks#

In this milestone we had to move our from our previous hosting. As possible solution, I hoped to use Mor.ph AppSpace and in this spring I continued the job, started in previous one to support EmForge working in Mor.ph environment. As result, we was able to test EmForge in cluster with two jetty used same DB and covered by one load-balancer. As result, different issues was found and fixed. More details about usage of EmForge in Clustered Environment you can see on EmForge Cluster page

Unfortunately, it was not possible to migrate our DB to the Mor.ph (due to some technical difficulties), so, migration task are still open (currently, I hope to move to Amazone EC2 during next month)

Better unit-testing and DB compatibility testing#

We finally returned back Continuous Integration Process (now, based on Hudson) and periodical running of compatibility tests for different DB. Now, you can see status of project (as well as status of DB Compatiblity testing) on our Hudson Page

Some improvement for properties management#

Now, it is possible to define own properties (to configure EmForge) in file config-user.properties, placed in same folder there standard EmForge config.properties placed. This file (config-user.properties) will override default properties. Keeping personal settings in separate file will allow you to keep this settings during upgrade (in case you are using MSI Installer) For more details please see EmForge Setup Guide

As always, some minor features as well as bug-fixes was implemented

Major Links:#

• EmForge-0.33 Milestone and closed tasks
• Download
• EmForge Quick Start
• EmForge Setup Guide
• EmForge Mail Lists
• EmForge Short Introduction