These failures seem to be related to not finding the new parent POM for m2 and then bad build state results.
I'm running the checkout ci early to get the new pom (this is not a continuum thing, but it'll make it available), then will build all if needed. - Brett [EMAIL PROTECTED] wrote: >Build statistics: > State: Unknown project state '0' > Previous State: Error > Started at: Thu, 1 Jan 1970 00:00:00 +0000 > Finished at: Thu, 1 Jan 1970 00:00:00 +0000 > Total time: 0s > Build Trigger: Schedule > Exit code: 0 > Building machine hostname: maven.zones.apache.org > Operating system : SunOS(unknown) > Java version : 1.4.2_09(Sun Microsystems Inc.) > > >**************************************************************************** >Output: >**************************************************************************** >There was no output. >**************************************************************************** > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
