[
https://issues.apache.org/jira/browse/FELIX-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044851#comment-13044851
]
Sahoo commented on FELIX-2982:
------------------------------
1. The change looks fine except that why not sleep(poll) before calling
initializeCurrentManagedBundles()?
2. Because directory watcher thread could be scheduled after any amount of
delay, the existing code does not ensure any lower bound for initial delay. In
such a case, I don't think there is really a change in promised behavior. Why
should we add yet another option in FileInstall, which is supposed to be a
simple management agent?
> noInitialDelay option does not work
> -----------------------------------
>
> Key: FELIX-2982
> URL: https://issues.apache.org/jira/browse/FELIX-2982
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Affects Versions: fileinstall-3.1.10
> Environment: fileinstall 3.1.10
> Reporter: Jonathan Anstey
> Assignee: Guillaume Nodet
> Attachments: FELIX-2982.patch
>
>
> The noInitialDelay option currently does not work - bundles are installed
> immediately regardless of the option's value. To reproduce this, I used
> Apache Karaf 2.2.1, which uses fileinstall 3.1.10. I edited the
> etc/org.apache.felix.fileinstall-deploy.cfg file to something like this:
> {code}
> felix.fileinstall.dir = ${karaf.base}/deploy
> felix.fileinstall.tmpdir = ${karaf.data}/generated-bundles
> felix.fileinstall.poll = 10000
> felix.fileinstall.noInitialDelay = false
> {code}
> I expected the jar I had in the deploy dir
> (http://repo1.maven.org/maven2/org/apache/camel/camel-core/2.7.2/camel-core-2.7.2.jar)
> to be installed 10 seconds after the container starts with this config,
> however it is installed immediately.
> Attaching a proposed fix for this shortly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
