ANN: Anthill Pro v.2.1.7 now available

Maciej Zawadzki <[email protected]> Fri, 07 Nov 2003 20:04:59 -0500
Newsgroups gmane.comp.java.anthill.announce
Organization Urbancode, Inc.
Message-ID <[email protected]>
Version 2.1.7 of Anthill Pro is now available.  This version focused
mostly on PVCS driver improvements as well as some bug fixes.  Memory 
utilization should be improved in this new build.  The complete list of 
changes is below.

You can download this latest release at
https://www.urbancode.com/products/anthillpro/secure/protected/download.jsp

-- issue #474 -- Handle illegal values for the "Path to Executable" 
property in VCS Driver edit screen.  Now, the value of this property can 
include the full path of the executable, including the exe.

-- issue #477 -- Automatic CVS login does not work under *nix.  The 
problem was that wen Anthill created the .cvspass file, the file was 
being created with wrong permissions.  Now, Anthill executes chmod 600 
on the file after it is created.

-- issue #657 -- Dependencies -- Always Rebuild setting is not 
persistent between Anthill restarts.

-- issue #659 -- PVCS error obtaining revision log from a branch.  The 
PVCS driver was not parsing the revision log correctly when revisions 
were performed on branches.  This has been fixed.

-- issue #660 -- Duplicate pagelet exception.  When using multiple build 
daemons, a race condition existed which could cause a Duplicate class 
definition exception.

-- issue #663 -- PVCS problems building from a label when some files do 
not have the label defined.  PVCS sometimes likes to exit with a return 
code of -13 (some unknown error).   This return code is now treated by 
Anthill as a valid return code.

-- issue #666 -- Email template fails when logs have not been created. 
When using the "complete" email template, failed builds caused the email 
generation step to fail.  This has been fixed.

-- issue #667 -- PVCS driver applies label to the trunk even when 
building a branch.  This has been fixed.

-- issue #668 -- Builders display stack trace when child process return 
code is not 0.  This was a aesthetic issue.  The stack trace is no 
longer displayed in the log.



Thanks,

--The Anthill Team