[
https://issues.apache.org/jira/browse/FELIX-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749480#action_12749480
]
Filippo Diotalevi commented on FELIX-1540:
------------------------------------------
>I do think we need to start all bundles managed by fileinstall that are not
>persistently stopped
That's my point.
In my use case, I didn't stop bundle-b-that-depends-from-a.jar , I just
temporarily removed the bundle-a.jar.
Therefore I expect that when I reintroduce the bundle-a.jar in the watched
folder, bundle-b-that-depends-from-a.jar is restarted.
> [FileInstall] When removing/re-adding a bundle, all the dependent bundles
> don't start anymore
> ---------------------------------------------------------------------------------------------
>
> Key: FELIX-1540
> URL: https://issues.apache.org/jira/browse/FELIX-1540
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Reporter: Filippo Diotalevi
>
> I'm experiencing this bug (or missing features) in the trunk; it may be
> related to FELIX-1482. The same feature was present in all the previous
> versions of File Install.
> I have 2 bundles in my ./load directory watched by File Install.
> -> bundle-a.jar ACTIVE
> -> bundle-b-that-depends-from-a.jar ACTIVE
> Now I remove bundle-a.jar, and remains only
> -> bundle-b-that-depends-from-a.jar INSTALLED
> I now I copy bundle-a.jar in the ./load file (or any other bundle that
> satisfy bundle b dependencies), I expected both the bundles to be active, but
> I get
> -> bundle-a.jar ACTIVE
> -> bundle-b-that-depends-from-a.jar INSTALLED
> So adding bundle-a does not start bundle-b-that-depends-from-a.jar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
