TagSEA version 0.6.4 has been released. For a list of new features, please visit our home page: http://tagsea.sourceforge.net
Updates the "Extras" feature to fix a bug which prevented Java Task Waypoints from discovering all Java Tasks (TODOs, FIXMEs, etc.).
Updates the "Logging" feature to log what information about what version/patch the user is using.
This patch fixes a bug in the date calculations for daily sends of TagSEA log files. This patch includes the fixes found in 1.2.0 as well.
Another patch has been made for the 0.6.2 stream. This patch addresses several issues including a fix for a possible memory leak that can occur after a workbench crash. This patch also includes the changes for previous patches. That means that this is the only patch that you need to install if you want to keep TagSEA up-to-date.
This patch fixes bug #165 "Error in scheduling network send jobs." In rare instances, it is possible that TagSEA will schedule sends of log data with high frequency in one day. It may occur if you are upgrading to Eclipse 3.3, copied all of your previous Eclipse preferences (not just using a previous workspace), had TagSEA set to upload logs every day, sent logs at the end of the previous day, and have no new logs to send. It may also occur in instances when exceptions are thrown during the attempt to send information. The bug will cause ui slowdown and may result in a memory error, due to an infinite scheduling of the "Sending TagSEA log data" job.... read more
A new version of TagSEA: 0.6.2 has been released. Nearly 40 bugs have been fixed, and several new features have been added. See our web page http://tagsea.sourceforge.net/ for more information.
On March 2nd, TagSEA version 0.6.0 was released. Nearly 40 bugs, features, and enhancements were addressed. See our home page http://tagsea.sourceforge.net for information.
The cvs repository for the TAGSea project will be populated and the first distributable made available soon (Admins are currently at a conference!). Check back next week!
Sign up for the SourceForge newsletter:No, thanks