continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject Re: Versioning the Continuum configuration
Date Sun, 21 Sep 2008 01:49:43 GMT
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
> <?xml version="1.0" encoding="UTF-8"?>
> <configuration>
> <version>2</version>
> -- 
> Wendy

Brett Porter

View raw message