[
https://issues.apache.org/jira/browse/FELIX-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845786#action_12845786
]
Guillaume Nodet commented on FELIX-2066:
----------------------------------------
I don't think calling resolve(null) is a good idea. Fileinstall should not
have any effect on bundles that are not managed by fileinstall, so we need to
compute the exact list of bundles that need to be resolved (same as the ones to
start ?) and only resolve those.
In addition, fileinstall has the feature to not resolve / start bundles at all
if the property felix.fileinstall.bundles.new.start is set to false. We should
keep this behavior, or maybe add a new property named
felix.fileinstall.bundles.new.resolve, so that people can configure fileinstall
to only resolve the bundles correctly but not start them.
> File Install fails to move fragment bundle into RESOLVED state
> --------------------------------------------------------------
>
> Key: FELIX-2066
> URL: https://issues.apache.org/jira/browse/FELIX-2066
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Environment: Windows XP, Java 6, Equinox , File-Install 2.0.8
> Reporter: Shrini Joshi
> Attachments: FELIX-2066.patch
>
>
> The file-install will install the fragment bundle but fails to move it to
> resolve. The fragment bundle remains in INSTALLED state.
> If we install it from equinox shell, then fragment bundle is installed and
> resolved correctly.
> Can someone please comment ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
