Yes, but my point is that it's not specified here http://docs.oracle.com/javase/6/docs/technotes/guides/jar/jar.html which is the specification of the _file format_. The fact that the jar tool happens to put the manifest first is immaterial since the file format specification just says that a jar is a zip file. Thus I should be able to create that file however I chose, not necessarily with the jar tool.
On 20 November 2015 at 13:28, Jan Willem Janssen < [email protected]> wrote: > > > On 20 Nov 2015, at 14:24, Tom Bentley <[email protected]> wrote: > > > > I'm experimenting with felix and I've noticed that it doesn't handle > > bundles which have a MANIFEST.MF which is not the first entry in the jar. > > As far as I'm aware it's not part of the jar specification that the > > manifest needs to come first, but having had a quick search of the > archives > > it seems this isn't the first time it's come up, so I thought I'd ask > for a > > reference before opening an issue. > > The manifest should always be the first entry for a JAR file to be valid, > which is specified, though not really clearly, see [1] for example. > > https://docs.oracle.com/javase/7/docs/technotes/tools/windows/jar.html > > -- > Met vriendelijke groeten | Kind regards > > Jan Willem Janssen | Software Architect > +31 631 765 814 > > My world is revolving around INAETICS and Amdatu > > Luminis Technologies B.V. > Churchillplein 1 > 7314 BZ Apeldoorn > +31 88 586 46 00 > > http://www.luminis-technologies.com > http://www.luminis.eu > > KvK (CoC) 09 16 28 93 > BTW (VAT) NL8169.78.566.B.01 > >
