Sorry, the description was not updated. The program started out in the
way described but then nobody wanted to use the variant, they wanted
to just created the XML. Due to some complications I decided to rip
out that functionality.

If you want, I can take a look at restoring it. However, maybe it is
easier then to make a program that reads the XML and creates the ZIP.

Kind regards,

     Peter Kriens
     
SEH> The description for the bindex¹ tool mentions the capability to create
SEH> a ZIP file of the referenced bundles:

SEH> ,----
SEH> | Additionally, it can simplify the URL handling handling by sweeping up
SEH> | all JAR files and placing them in a ZIP file, together with the
SEH> | repository.xml file. This ZIP file can be unzipped in a convenient
SEH> | place on a web server. The program takes care of many naming issues
SEH> | that arise when you try to create a repository. Alternatively, it can
SEH> | recurse over a directory structure and just creates a repository.xml
SEH> | file. The URLs in that case can be rewritten useing[sic] a template.
SEH> `----

SEH> This makes it sound as though bindex will operate in one of two modes:
SEH> scan a directory structure and create a repository.xml file describing
SEH> what it found, or create a ZIP file of all the bundles it finds,
SEH> perhaps renaming them to solve some of these "naming issues".

SEH> I can't figure out how to elicit the latter behavior. Specifying a
SEH> name for the repository file ending with ".zip" does cause bindex to
SEH> create a ZIP file, but the only member is the repository.xml file,
SEH> regardless of how many JARs I tell bindex to read.

SEH> Was this promise of creating an archive of the bundles never
SEH> implemented?


SEH> Footnotes: 
SEH> ¹ http://www2.osgi.org/Repository/BIndex



-- 
Peter Kriens                              Tel +33467542167
9C, Avenue St. Drézéry                    AOL,Yahoo: pkriens
34160 Beaulieu, France                    ICQ 255570717
Skype pkriens                             Fax +1 8153772599

_______________________________________________
OSGi Developer Mail List
[EMAIL PROTECTED]
http://www2.osgi.org/mailman/listinfo/osgi-dev

Reply via email to