There is some discussion on dev@continuum about using Liquibase for this. http://www.liquibase.org/ (It's LGPL though...)

LGPL isn't really an issue for us because we wont redistribute it directly

If i remember correctly, Archiva dev had to yank out jasperreport a LGPL type license out of archiva distribution.

What is the different if we use lidquibase for the automatic db upgrade?

It isn't the same case.

We can't use jasperreport because we can't distribute it with Archiva.
About liquibase, we have nothing to distribute because users will can download it directly or use the maven plugin like it can use the checkstyle plugin with Checkstyle under LGPL. We have nothing to distribute.

Dan is talking about an automatic database upgrade, which would imply that Archiva can do it with no user intervention.

Wait a sec, why can't you use LGPL?
Isn't it the point of LGPL that you can use it without the rest of your code being under the same lic?

Brill: http://www.apache.org/legal/resolved.html

It cannot be required in a default installation as it affects the license of the overall work.

review if this is an issue for 1.1 -> 1.2

no issue in upgrading now

we ensure the redback database autoupgrades, and the archiva database has been removed