The only real changes that come to my mind right now are: support for JBoss AS 7 and a minor bugfix related to pagination. But since the last release is getting quite old now, I’m looking forward to release a minor update within the next few weeks.

• Move to Git
  I’m not sure whether it is because of SourceForge being so slow or because of Subversion itself, but working with the SVN repository seems terribly painful. With all the cool kids moving to Git, it’s probably time to follow suit.
• Put out one or more Feature Releases (1.1, …)
  Some feature requests have already been posted in the tracker and some of them should better be implemented sooner than later.
• Put out Framework Release (2.0?)
  I have often stated that I envision LogSaw as a framework that everyone and his dog can build upon to parse and analyze arbitrary log files or even other data. This will require a major re-engineering effort so it will definitely take some time. But on the other hand, it’s definitely a challenge I’m looking forward to

On the bright side of things, I have pimped the documentation infrastructure a bit more and enabled it to export the documentation as PDF as well. This might come in handy, because I still need to find some shape or another to post the documentation onto this website.

So, bottom line is it’s atleast another week until the RC will be ready on my end — and I just hope the Buckminster folks can deliver sometime soon.

Now, the bad news is that I’m again behind schedule. That’s partly due to the help infrastructure stuff being rather tricky, but also due to me appreciating the world cup too much So the M4 will probably slip into early July without P2-enablement (read: the update feature). That will then be included in a Milestone 5. More details on this once M4 is out of the door.

That’s not ment to say that where isn’t alot of potential for improvement though, which brings us back on topic…
There will be a Milestone 4, but it will feature just two things over M3: 1) P2-enablement and 2) user documentation. This Milestone is currently targeted for the end of the month; it will then be followed by one or more RCs (if necessary) and the final 1.0 bits by mid-July.

If you followed the project a bit, you know that the mission states that it should also provide a framework for developers to build their own log file parsers on; but frankly, I feel that this part isn’t mature enough yet. I have been playing around with OSGI Declarative Services lately and it undoubtly has a few advantages over the current Eclipse extension point approach, but incorporating these changes into 1.0 would completely screw the schedule.

Long story short, expect the framework stuff to come into life with 1.1.

The reasons for this are manifold. First I have fixed alot of rather nasty parsing bugs that I encountered during testing, which alone would justify a release. Also I have finished a really huge reengineering, that should definitely improve overall application robustness. And finally, the WebSphere support is rocking now

Though, I will have to fix another bug and add a few more JUnit tests, before M3 will be rolling out. Stay tuned.

• M2: April 19th – Usability improvements
• M3: May 19th – WebSphere dialect, overall documentation, <insert your feature request here>
• RC: Early June – P2 update function
• Final: mid-June

After release of 1.0.0, work will continue immediately on 1.1 which will be based on Eclipse Platform 3.6. If you have any super cool feature requests that you would like to see in 1.0, feel free to post them in the comments or open a ticket in our SourceForge.net tracker.