dotCMS 1.6 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News dotCMS 1.6 (Default branch)
# 1  
Old 05-14-2008
dotCMS 1.6 (Default branch)

ImagedotCMS is a complete J2EE Web CMS/CRM system thatis built into a JSR-168-compatible portal. dotCMSis intended to bridge the gap between the PHP CMSofferings and the J2EE document managementsolutions with bolted on Web CMS. It offers a richstructured content engine, content widgets andmacros, customer management, user tracking, clickpath reporting, eMarketing list management,eNewsletter/email campaign managers, and a Web 2.0calendar of events.License: GNU General Public License (GPL)Changes:
Over 300 improvements and fixes were made. Thepackage now includes a full starter site withexample templates, CSS, widgets, and a Web 2.0calendar. LDAP integration was improved. Tomcatwas upgraded to 6.0. i18n is supported.Performance enhancements were made. Sitewideimport/export functionality was made. Numerous newwidgets and macros were added to provide richcontent functionality.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)