Hi Tom, I stumbled over that problem also in past, when creating JAR files just with a zip tool. As Jan mentioned, the MANIFEST file must be first file, as processing of other JAR entries may depend on MANIFEST content.
See a very old bug at http://bugs.java.com/bugdatabase/view_bug.do?bug_id=4405744, that spec is not accurate enough. I recommend to adapt your compiler to use tool like jar for correct creation of JAR file, which could include other options like signing, INDEX file and more. Bye, Jochen On Fri, Nov 20, 2015 at 3:08 PM, Tom Bentley <t.j.bent...@gmail.com> wrote: > Hi Frank, > > I work on the JVM compiler for the Ceylon programming language and Felix is > having problems consuming the jars our compiler produces (they're called > .car files, but they following the jar specification). > > I suspect Felix is not the only product which replies on having the > MANIFEST.MF first, so we'll probably just have to change the compiler. For > reference: https://github.com/ceylon/ceylon/issues/5750 > > Cheers, > > Tom > > On 20 November 2015 at 13:41, Frank Langel <fr...@frankjlangel.com> wrote: > > > Hi Tom, > > > > > > What is it you are trying to do ? OSGI/Felix expects a jar file with a > > certain format. > > Your question is not quite clear. How can we help? > > > > > > On 11/20/15, 2:35 PM, "Tom Bentley" <t.j.bent...@gmail.com> wrote: > > > > >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 < > > >janwillem.jans...@luminis.eu> wrote: > > > > > >> > > >> > On 20 Nov 2015, at 14:24, Tom Bentley <t.j.bent...@gmail.com> > 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 > > >> > > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > > For additional commands, e-mail: users-h...@felix.apache.org > > > > >
