ObjectWeb Consortium
Search ObjectWeb Mail Archive: 

Advanced Search - Powered by Google

Mail Archive Home | oscar List | Febuary 2005 Index

<--  Date Index  --> <--  Thread Index  -->

Re: [oscar] New obr

Regarding OBR docs, that is probably my fault, since I didn't do a very good job of documenting the changes. OBR started out as a quick hack, but it still surprises me that people use it pretty seriously. :-) In future updates, I will try to keep this in mind better. Sorry.

Regarding mirroring OBR, there is no specific support for this. It seems like it might be possible to somewhat automate it by using some sort of web site crawler to crawl the OBR main page and save what it finds, but other than that, I don't have an idea.

-> richard


That sounds perfect. I am sorry I did not read the previous message that explained all 
that. Wouldn't it be worthfull to mention this in the "Bundle Repository 
Changes" web page ? I guess it is part of the changes from version 1.1.0 to 1.1.1, 
which are not listed on the web page.

I have now a new question concerning obr : is there a way to build a local copy of a 
given bundle repository in an "automated" way (something like a mirror) ?
More precisely, the practical usage : we would like to use obr for deployment on machines having no access to Internet. Thus, I have built a copy of the oscar-osgi.sf.net obr more or less by hand, onto a local machine that can be connected to Internet AND to the local network. I would like to automate this process.
Thank you for your help,

-----Message d'origine-----
De : Richard S. Hall [mailto:heavy@xxxxxxxxxxxxxx] Envoyé : mercredi 23 février 2005 14:53
Cc : oscar
Objet : Re: [oscar] New HTTP Shell bundle


For those who maintain a private repository for home developped bundles (like 
we do here at France Telecom Grenoble), and thus redefine 
oscar.repository.url to contain several repository urls (our own repository 
and oscars' standard repository).

We have to update obr
We must replace in our oscar.repository.url property

Am I right ?

Yes, you are correct. However, see below.

Also, is there a change in the repository.xml syntax ? I guess not.

There was a slight change, I added a <repository> tag, like this:

   <name>Oscar Bundle Repository</name>
   <date>Fri May 07 16:45:07 CEST 2004</date>

This tag identifies the repository and adds the ability for the repository to 
link to external repositories. As I mentioned before, this was a quick 
attempt to address some issues that we were having with making independent 
repositories visible in/on OBR, but also having them be independently 
managed. This is only a small step toward supporting multiple, independent 

Currently, OBR will only parse one level of external repositories, but it is 
programmed so that in the future we can recurse an arbitrary number of hops; 
thus, we might have a federation of repositories, where each repository 
references other repositories. However, this must wait until other features 
are implemented, but at least it is a start.

For now, given your situation, you can use this <extern-repositories> tag to 
create your own top-level repository file that links to OBR and any other 
repository XML file, then just set your oscar.repository.url property to point to 
this new top-level repository file. It will automatically merge all of the 
referenced URLs. Then you only need to edit the XML file to add 
bundles/repositories to your local OBR instances.

Does that make sense?

-> richard


You receive this message as a subscriber of the oscar@xxxxxxxxxxxxx mailing 
To unsubscribe: mailto:oscar-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.