I agree that for the given reasons unpacking and overlaying JARs is not a good option. When working with Bundles in Eclipse it is possible to place JAR dependencies directly into the projects and add them to the bundle classpath. I understand that Embed-Dependency inline=false does the same thing and should be preferred.
- Richard Richard Eckart de Castilho Am 19.07.2011 um 21:44 schrieb Marshall Schor: > Thanks, Richard. > > I think you are right - some of the dependencies (for example, the > AlchemyApiAnnotator depends on Apache commons-digester, etc.) don't have OSGi > packagings. > > The build strategy for the OSGi modules currently gets all the dependencies > and > unpacks them into .../target/classes directory, where a later step "jars" > them up. > > This approach overlays files being unzipped, with later versions. Some > examples > where this might be an issue: > There is at the top level a license directory, containing one "LICENSE" file. > There is at the top level a "plugin.xml" file. > There is at the top level a META-INF dir, with LICENSE and NOTICE files among > other things. > > Perhaps it would be better to package the dependencies that are not OSGi in a > way that doesn't need to unpack, and then potentially overlay, files. > > It seems that OSGi and the bundle plugin support this, via the > Embed-Dependency > instruction. Is there a reason we're not using that, instead of the > "unpacking" > approach? > > -Marshall -- ------------------------------------------------------------------- Richard Eckart de Castilho Technical Lead Ubiquitous Knowledge Processing Lab FB 20 Computer Science Department Technische Universität Darmstadt Hochschulstr. 10, D-64289 Darmstadt, Germany phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117 eckar...@tk.informatik.tu-darmstadt.de www.ukp.tu-darmstadt.de Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de -------------------------------------------------------------------
