gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew McIntyre <>
Subject Re: BATCH: All dressed up, with nowhere to go...
Date Fri, 19 Aug 2005 20:29:41 GMT

On Aug 19, 2005, at 5:27 AM, wrote:

> 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"
> /x1/gump/public/workspace/db-derby/build.xml:770: The following  
> error occurred while executing this line:
> /x1/gump/public/workspace/db-derby/build.xml:849: Invalid  
> Manifest: /x1/gump/public/workspace/db-derby/jars/insane/lists/

I'm unable to reproduce this error myself. From the error, it would  
seem that Ant has generated a bad manifest file in the <manifest>  
task of the derbyjarwithoutosgi target, presumably by putting space  
between the other top-level attributes and the top-level "Sealed"  
attribute. Works for me in my view, though. Is this maybe an Ant  
issue? Or stale files hanging around somehow?

Would it be possible to get access to the bad manifest to better  
understand the problem?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message