Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 90141 invoked from network); 21 Sep 2008 01:51:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Sep 2008 01:51:23 -0000 Received: (qmail 23390 invoked by uid 500); 21 Sep 2008 01:51:20 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 23327 invoked by uid 500); 21 Sep 2008 01:51:19 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 23316 invoked by uid 99); 21 Sep 2008 01:51:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Sep 2008 18:51:19 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [210.50.30.235] (HELO mx05.syd.iprimus.net.au) (210.50.30.235) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Sep 2008 01:50:17 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjIBACZF1Ug6sheF/2dsb2JhbAAItW6BZg X-IronPort-AV: E=Sophos;i="4.32,439,1217772000"; d="scan'208";a="144605346" Received: from 133.095.dsl.syd.iprimus.net.au (HELO [172.16.237.15]) ([58.178.23.133]) by smtp05.syd.iprimus.net.au with ESMTP; 21 Sep 2008 11:49:48 +1000 Message-Id: <9459F1FC-785D-4F77-8BF5-5CE52EFF3F38@apache.org> From: Brett Porter To: dev@continuum.apache.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Subject: Re: Versioning the Continuum configuration Date: Sun, 21 Sep 2008 11:49:43 +1000 References: X-Mailer: Apple Mail (2.929.2) X-Virus-Checked: Checked by ClamAV on apache.org Yep, Archiva automatically updates an out of date configuration file on save and can read old versions. I think in terms of the database - we do already have a version in there (it should be storing the modelVersion as long as we're doing that consistently). I'm ready to toss out data-management calling it "it seemed like a good idea at the time" and use standard database backup techniques and SQL based migrations. I think Emmanuel has suggested tools in the past. The way Rails does it is ideal - surely someone has knocked that up in Java already? :) I'm pretty sure I also saw something in the OpenJPA documentation too, though haven't had a chance to investigate. Perhaps Ken could comment on this? - Brett On 20/09/2008, at 8:33 AM, Wendy Smoak wrote: > I wrote a while back about versioning the Continuum database... I > think the same is going to apply to the continuum.xml configuration > file. > > Changes in the structure of that file are inevitable, and Continuum > needs to be able to figure out what version it's working with. The > Archiva devs who hang out here can probably comment-- I think they've > been through this already. :) > > $ cat archiva.xml > > > 2 > > -- > Wendy -- Brett Porter brett@apache.org http://blogs.exist.com/bporter/