ANN: Anthill Pro v.2.1.4 (2.1 preview) now available
Maciej Zawadzki <[email protected]> Wed, 20 Aug 2003 08:23:59 -0400
| Newsgroups | gmane.comp.java.anthill.announce |
|---|---|
| Organization | Urbancode, Inc. |
| Message-ID | <[email protected]> |
Version 2.1.4 of Anthill Pro is now available. This version focused mostly on a few bug fixes as well as implementing a few requested features. The list of changes is below. You can download this latest release at https://www.urbancode.com/products/anthillpro/secure/protected/download.jsp Thanks, --The Anthill Team -- issue #480 -- "Build as" build optionally not reset the version for future builds. The "build as" option now contains two text boxes -- the first text box specifies the version to be used for this build and it is required; the second text box specifies the version number to be used on the build after this one (this text box is optional). With these two text boxes, if you are currently at version "1.2.3" and want to build as "1.2.4 alpha" but then want to drop the alpha designation from all future builds, you'd enter "1.2.4 alpha" in the first text box and "1.2.5" in the second text box. This example assumes that the version format is "x.y.b" where b is the build number. -- issue #569 -- Multi-threaded builds throwing VSS errors. This problem occurred on Windows because the VCS Driver library creates temporary batch files that hold the VCS commands. The problem was that the patch files always had the same name. So if two threads were doing a build at the same time, both of them may try to write to and then execute the same batch file. This has been fixed so each generated batch file now has a unique name, thus guaranteeing that there are no thread collisions. This does not completely fix the multi-threaded build problem, since the logs are still not bound to any one thread; they are shared by all threads and thus can contain output from other concurrently running builds. -- issue #576 -- Ant builder commands not being quoted. This problem was introduced in version 2.1.3.346 when we started using a new utility library to execute Ant commands. The problem manifests itself as strange Ant builder failures when any of the paths or the version number contain spaces. -- issue #577 -- Specification Property Based Versioning Strategy exception during edit. -- issue #578 -- Support for environment variables in Make builder. The Make builder now supports the setting of environment variables just like the Ant builder does. -- issue #579 -- Maven builder goals not getting restored or copied. This problem was introduced in 2.1.3.346. -- issue #580 -- Project Counter is not being created when a new project is created. A new project level Counter is now being created whenever a new project is created or copied from an existing project. -- issue #581 -- Maven builder not handling Maven return codes. The Maven builder now inspects the Maven return code and prints out a message indicating the cause of the failure. The build is marked as having failed in the event of a Maven return code that indicates a Maven build failure. -- issue #582 -- Maven builder exceptions after deletion. Maven builders were not being deleted completely from Build Tracks, causing possible exceptions after attempted deletion.