felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shrini Joshi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-2066) File Install fails to move fragment bundle into RESOLVED state
Date Tue, 16 Mar 2010 17:34:27 GMT

    [ https://issues.apache.org/jira/browse/FELIX-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846017#action_12846017
] 

Shrini Joshi commented on FELIX-2066:
-------------------------------------

I can see that submitted patch clearly misses to address above use case.


"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."
To refine above point - we should compute all those unresolved bundles handled by file install.

But I believe property "felix.fileinstall.bundles.new.start" affects only the startup action
and resolve action is not affected by its value. So in other words, file install always tries
to resolve bundle but the decision of starting is driven by above mentioned flag. 

Do you think I got this right?




> 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.


Mime
View raw message