LiquiBase 1.5.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News LiquiBase 1.5.0 (Default branch)
# 1  
Old 01-29-2008
LiquiBase 1.5.0 (Default branch)

LiquiBase is a DBMS-independent library fortracking, managing, and applying database changes.It is built on a simple premise: all databasechanges (structure and data) are stored in anXML-based descriptive manner and checked intosource control. While there have been manyattempts to provide a similar tool, LiquiBase aimsto provide a solution that supports merging ofchanges from multiple developers, works well withcode branches, supports a database refactoringIDE/plugin, and more.License: GNU Lesser General Public License (LGPL)Changes:
This release includes major code refactoring along with several important new features.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
ARCHPATH(1)						      General Commands Manual						       ARCHPATH(1)

NAME
archpath - output arch (tla/Bazaar) archive names, with support for branches SYNOPSIS
archpath archpath branch archpath branch--version DESCRIPTION
archpath is intended to be run in an arch (tla or Bazaar) working copy. In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working copy. If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current archive and category and with the same version as the current working copy. This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a com- mand like this: baz branch $(archpath) $(archpath new-feature) Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this: baz branch $(archpath) $(archpath releases--1.0) That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result. AUTHOR
archpath was written by Colin Watson <cjwatson@debian.org>. Like archpath, this manual page is released under the GNU General Public License, version 2 or later. DEBIAN
Debian Utilities ARCHPATH(1)