continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wendy Smoak <>
Subject Re: Problems in Data Management
Date Sat, 11 Apr 2009 05:23:04 GMT
On Fri, Apr 10, 2009 at 8:03 PM, Wendy Smoak <> wrote:

> I can export the vmbuild data from 1.2, but I can't import it into
> 1.3.2.  Marica reported this a while ago:
> I'm going to try with 1.3.3-SNAPSHOT next, in case it has been fixed
> already and I didn't notice.

Success!  CONTINUUM-1912 was actually duplicated by CONTINUUM-2100,
and _that_ was fixed in 1.3.3.  So I can import the vmbuild data into
1.3.3-SNAPSHOT, [and fix the NEXT_VAL values], however the app doesn't
seem to want to start up afterwards.  It's hanging (30 minutes now,
and Error 503 in the browser) at

2009-04-10 21:51:15,023 [WrapperSimpleAppMain] INFO
org.apache.maven.continuum.DefaultContinuum  - Initializing Continuum.
2009-04-10 21:51:15,023 [WrapperSimpleAppMain] INFO
org.apache.maven.continuum.DefaultContinuum  - Showing all groups:

A normal startup would say 'Showing all projects' next and then print
the welcome message with the cow.

> ... is it possible to make changes
> so that it's not necessary to export-and-import, and pointing 1.3.3 at
> a 1.2.x database Just Works?

Pointing 1.3.3-SNAPSHOT at the 1.2 database definitely doesn't work:

2009-04-10 20:43:32,000 [WrapperSimpleAppMain] ERROR JPOX.RDBMS  - An
exception was thrown while adding/validating class(es) : In an ALTER
TABLE statement, the column 'DISTRIBUTED_BUILD_ENABLED' has been
specified as NOT NULL and either the DEFAULT clause was not specified
or was specified as DEFAULT NULL.

Can we provide a default value (false) for DISTRIBUTED_BUILD_ENABLED?


View raw message