The description for the bindex¹ tool mentions the capability to create a ZIP file of the referenced bundles:
,---- | Additionally, it can simplify the URL handling handling by sweeping up | all JAR files and placing them in a ZIP file, together with the | repository.xml file. This ZIP file can be unzipped in a convenient | place on a web server. The program takes care of many naming issues | that arise when you try to create a repository. Alternatively, it can | recurse over a directory structure and just creates a repository.xml | file. The URLs in that case can be rewritten useing[sic] a template. `---- This makes it sound as though bindex will operate in one of two modes: scan a directory structure and create a repository.xml file describing what it found, or create a ZIP file of all the bundles it finds, perhaps renaming them to solve some of these "naming issues". I can't figure out how to elicit the latter behavior. Specifying a name for the repository file ending with ".zip" does cause bindex to create a ZIP file, but the only member is the repository.xml file, regardless of how many JARs I tell bindex to read. Was this promise of creating an archive of the bundles never implemented? Footnotes: ¹ http://www2.osgi.org/Repository/BIndex -- Steven E. Harris _______________________________________________ OSGi Developer Mail List [EMAIL PROTECTED] http://www2.osgi.org/mailman/listinfo/osgi-dev
