[EMAIL PROTECTED] wrote:
I find the cache concept more useful than profiles. The behavior I would prefer is to launch Felix and have it use a default cache directory (~/.felix), which I could override through a command line argument or system property. I don't find the interactive mode useful.
To me, a single global default doesn't make so much sense...which is why I introduced the profile concept in the first place.
Configuration via properties will definitely be the case, as is now, which does allow you to avoid interactivity.
Actually, during development I find that my bundles change so frequently that the cache becomes more of a burden than an advantage. I have a script that deletes my cache directory before launching Felix, so that I know I'm looking at fresh code. I'd like to have an argument to Felix that would suppress caching entirely, or flush the cache on startup.
Suppressing the cache entirely is not easy or feasible in all cases. However, flushing the cache is possible and has been asked for before.
-> richard
//P -- Parker Abercrombie The Okori Group, LLC On Tue, 07 Oct 2008 16:25:12 -0400, "Richard S. Hall" <[EMAIL PROTECTED]> wrote:I am going to be making some changes to how Felix creates bundle caches. Currently, when you create an instance of Felix it needs one of the following pieces of information to create a bundle cache: * Profile name - in which case it creates a directory named after the profile name inside the default "~/.felix" profile directory for caching bundles (you can also specify a cache directory and a profile name) or * Profile directory - in which case it caches the bundles in the specified directory directly. The change that I want to make is so that it is possible to start Felix without specifying any information, in which case it would default to creating a bundle cache directory (e.g., "felix-cache") in the current working directory. This change seems simple enough, but then I started to wonder about the profile notion altogether. I wonder if people feel we should keep the profile notion or get rid of it. If we got rid of it, we could still have something similar. For example, we could modify the launcher to ask for a cache directory, instead of a profile name. The resulting behavior would be something like: 1. If the user just hits return (i.e., doesn't specify anything) then the default "felix-cache" directory is created/used in the current working directory. 2. If the user types a simple name (e.g., "mycache") then a corresponding directory is created/used in the current working directory. 3. If the user types an absolute directory name, then that directory is used/created for the bundle cache. If the user wanted a similar "profile" experience just use simple names, where the main difference is that the profiles are kept locally. If you want profiles kept globally, then just specify the full path. The profile notion is merely a convenience and we could still mimic it completely in the launcher if people still like it as a convenience, so it is not necessarily an either-or situation. But if most people do not find the profile concept useful, then there is no reason to keep dragging it along since I will be making changes in this area now. It would also be possible to go further an not have the launcher be interactive at all and only accept this information through properties. I know that Oscar had "profiles" since the beginning, but that doesn't mean that we cannot question them. :-) Thoughts? -> richard--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
