Hi andrew, Don't really understand the problem but I've put the db-derby dir from vmgump at
http://vmgump.apache.org/derby-gump-snapshot.tgz please holler when we can remove it. cheers! Leo On Tue, Oct 25, 2005 at 03:11:01PM -0700, Andrew McIntyre wrote: > Just noticed that this is still failing. I am unable to reproduce the > problem. Please see my previous mail concerning this problem. It would > appear on the surface to be an issue with how Ant generates the > manifest file in the derbyjarwithoutosgi target. Is there any way > that I can get access to the manifest file in the zone where gump is > run to compare with a copy generated outside of the gump run? > > cheers, > andrew > > > On 10/25/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > *********************************************************** G U M P > > ... > > [EMAIL PROTECTED]: Project derby (in module db-derby) failed > >... > > <snip> other failures > > *********************************************************** G U M P > > [EMAIL PROTECTED]: Project derby (in module db-derby) failed > > <snip other targets> > > > > derbyjarwithoutosgi: > > [jar] Building jar: > > /x1/gump/public/workspace/db-derby/jars/insane/derby.jar > > [jar] Manifest is invalid: Manifest sections should start with a > > "Name" attribute and not "Sealed" > > > > BUILD FAILED > > /x1/gump/public/workspace/db-derby/build.xml:775: The following error > > occurred while executing this line: > > /x1/gump/public/workspace/db-derby/build.xml:854: Invalid Manifest: > > /x1/gump/public/workspace/db-derby/jars/insane/lists/smf.mf > > --------------------------------------------------------------------- > 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]
