+1 A vector solution would fix the problem I've been having. I am willing to code or test this change given direction.
Is there a specification somewhere on the changes that ant wants to make in the manifest? I know that it adds a Created-By, and a Manifest-Version when not present. Richard -----Original Message----- From: Paul Cody [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Tuesday, March 12, 2002 2:48 PM To: 'Ant Users List' Subject: RE: Using Main-Class and Class-Path in a manifest file > > I can't confirm that Class-Path is needed first, but I can > confirm that > ant 1.4.1 scrambles the order of entries in the Manifest. This has > caused me problems to such a degree, that I just went back to > using ant > 1.3. I posted a message about it a few days ago, I didn't get a > response, and haven't had time to get back to it. > > The bug seems to be that ant rearranges. > > Richard > I certainly agree that ant should maintain the ordering given to it. The fix would be to just use a Vector rather than a Hashtable. Attribute lookups within a Section would be barely slower, but since this is such a rare operation and since the number of attributes within a section is always small, even linear search is perfectly appropriate. Paul -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: < mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
