I am finalizing an add-on chapter section about the Roobot and OBR repositories, and I noticed that when you add an OSGi OBR command such as
osgi obr url add --url ...
it only keeps the OBR in memory, and has no future information about it. Is this as designed? Bear with me here...
I'm thinking that companies may want to provide their own internal add-ons so that they can improve their internal productivity (here's my Roo JSF platform, customized to taste, or a fork of the GWT configuration, or an integration library and Spring facades, etc).
One option I guess would be to store the OBRs you configure in a list in config, but I'm not a big fan of that, especially if things get screwed up. What if we were able to add a startup.roo script to a ~/.roo/startup.roo, so that we could automatically run scripts on startup for power users or corporate setups? Seems to me we could do a lot there to customize the footprint and visibility of add-ons.