In the majority of case, they aren't really warns/errors but only information message that don't be correctly categorized in sub-components we use. derby schema error: it's a message return by derby to jpox(jdo) when jpox check the database existence before to create it. BUILDDEFINITION.LATEST_BUILD_ID...: We can't specify the default value for schema compatibility with old continuum database (jpox message) velocity error: not an error but velocity is sometimes too verbose "There was no such logger": plexus debug message that we need to remove in plexus. Emmanuel Simon Kitching a écrit : > Hi, > > > I'm just starting to use Continuum, and decided to start with the current RC > (20060414). > There are a number of warning/error messages emitted by continuum that might > be better handled. > None of this appears to stop Continuum from working however. I'm reporting > these as the RC > vote is currently underway; not sure that any of this is worth holding back > a release for though. > Still, warn/errors on startup aren't a great introduction for new users.. > > ----- > On startup of a new installation, this appears: > > > jvm 1 | 2006-04-20 11:33:03,257 [WrapperSimpleAppMain] WARN RDBMS > > - Error initialising derby schema : Schema 'SA' does not > exist > jvm 1 | ERROR 42Y07: Schema 'SA' does not exist > > jvm 1 | at > org.apache.derby.iapi.error.StandardException.newException(Un > known Source) > > > > This only occurs when the database doesn't exist (eg on first startup). It > might be > nice to check for this, and avoid issuing this warning in this particular > case. > > ==================================== > On every startup this appears: > > - Column BUILDDEFINITION.LATEST_BUILD_ID should not allow nulls b > ut does. You can prevent nulls by specifying "allows-null" as "false" for > the ield> in the MetaData > > > > Presumably this can be fixed by following the advice in the message... > > > e.execution.TaskQueueExecutor,build-project] > > jvm 1 | 2006-04-20 11:47:50,751 [WrapperSimpleAppMain] ERROR > VelocityComponen > t - ResourceManager.getResource() parse exception: > org.apache.veloc > ity.exception.ParseErrorException: Lexical error: > org.apache.velocity.runtime.pa > rser.TokenMgrError: Lexical error at line 121, column 17. Encountered: > af > ter : "" > > > > I've got no idea what this is about... > > ==================================== > On shutdown lots of lines like this appear: > > jvm 2 | There was no such logger 'org.codehaus.plexus.ircbot.IrcBot' > 26986262 > . > > jvm 2 | There was no such logger > 'org.apache.maven.continuum.configuration.Co > nfigurationService' 26986262. > > jvm 2 | There was no such logger > 'org.apache.maven.continuum.execution.maven. > m2.MavenBuilderHelper' 26986262. > > > > > Regards, > > Simon > > > > >