In that case you could try: - start your app with the previous config - create the new folder - move the folder contents - update the config
The main thing is that it needs to be running to detect changes - though I don't know if that's a deliberate design. Cheers, Chris On 12 May 2010 16:39, Sahoo <[email protected]> wrote: > If I clear framework cache, then fileinstall will definitely pick up new > configuration, but I can't afford to clear framework cache as it also > contains bundles installed by user. > > No, fileinstall 3.0 does not create the watched dir. > > Thanks, > Sahoo > > > On Wednesday 12 May 2010 09:01 PM, Christopher Brind wrote: > >> Did you try stopping your app then clearing your Felix cache and the work >> directory created by Fileinstall? >> >> (I'm assuming it still creates one, I haven't used 3.0 yet.) >> >> Cheers, >> Chris >> >> >> On 12 May 2010 16:20, Sahoo<[email protected]> wrote: >> >> >> >>> I would like someone to confirm if the observed behavior is a bug or not. >>> It looks like a bug to me. I have a watched directory configured via >>> system >>> property felix.fileinstall.dir. In that watched directory, I have a cfg >>> file >>> called org.apache.felix.fileinstall-autodeploy.cfg which contains >>> felix.fileinstall.dir=/tmp/foo/. >>> It was working fine. I wanted to move foo to bar. So, I stopped my app, >>> updated the dir name in existing >>> org.apache.felix.fileinstall-autodeploy.cfg >>> file and restarted my app. I still see fileinstall trying to watch >>> /tmp/foo >>> instead of /tmp/bar. >>> >>> I am on fileinstall 3.0. >>> >>> Thanks, >>> Sahoo >>> >>> >>> --------------------------------------------------------------------- >>> 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] > >
