[
https://issues.apache.org/jira/browse/FELIX-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675302#action_12675302
]
Peter Kriens commented on FELIX-937:
------------------------------------
I think the problem is that there should be no overlap so the error is what you
want.
The purpose of FileInstall is to act as a manager. That is, you reuse the
operating systems file management tools (which are usually terrific: drag and
drop, shell, wildcard) to manage your bundle. The power is that it is very
simple to understand. I think you will make file install a lot more murky when
you start making it handle other management agents.
> FileInstall can't handle autostart bundles that are part of watched directory
> -----------------------------------------------------------------------------
>
> Key: FELIX-937
> URL: https://issues.apache.org/jira/browse/FELIX-937
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Environment: generic
> Reporter: Sahoo
>
> Let's say you configure File Install to watch directory /tmp/modules and
> there is a bundle called /modules/foo.jar which is specified as an autostart
> bundle. In Felix's config.properties, autostart bundles are specified using
> URLs (file:///modules/foo.jar in this case) which is internally used as the
> location of the bundle as well. On the other hand, File Install uses
> "absolute path" (/modules/foo.jar in this case) as the location. As a result,
> when File Install tries to install the same bundle, it gets the following
> error:
> INFO: failed to install/start bundle: : org.osgi.framework.BundleException:
> Could not create bundle object.
> This is caused by org.osgi.framework.BundleException: Bundle symbolic name
> and version are not unique.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
