Well, at least in my experience so far, for libraries, it is usually enough to take the default manifest, if there is a version of the jar available that has one, but for frameworks, you may want to customize exactly what packages are depended upon and, more importantly, what dependencies are bundled in the jar. For example, for the Struts 2 bundle, I wanted XWork, OGNL, Freemarker, and several Struts 2 plugins in the bundle, so I ended up constructing my own bundle with its own OSGi headers. Freemarker just wasn't working, for whatever reason, when deployed as its own bundle, and packaging the rest of the deps into the struts bundle made deployment a lot easier. I've found if you can reduce the number of bundles you deploy, the less complicated your life will become.
That said, adding OSGi manifest entries to your library would certainly be appreciated. Don On Mon, Jul 14, 2008 at 5:42 PM, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > 2008/7/14 Don Brown <[EMAIL PROTECTED]>: >> Actually, that bit isn't a problem - we could bundle the tiles jars in >> the struts 2 tiles plugin and generate the manifest for both >> automatically. > > Sorry for the dumb question, but does "bundling" mean "decompress and > recompress together"? IMHO it's easier to add a bunch of lines in the > manifest of Tiles jars than decompressing and recompressing jars. > I suppose it's not difficult, so probably it could be added in Tiles > 2.0.7 (the latest version is 2.0.6). > > Antonio > > --------------------------------------------------------------------- > 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]
