You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Tobias (JIRA)" <ji...@apache.org> on 2010/10/31 07:01:20 UTC
[jira] Created: (FELIX-2678) Startlevel for bundles in
auto.deploy.dir
Startlevel for bundles in auto.deploy.dir
-----------------------------------------
Key: FELIX-2678
URL: https://issues.apache.org/jira/browse/FELIX-2678
Project: Felix
Issue Type: New Feature
Components: Framework
Affects Versions: framework-3.0.5
Reporter: Tobias
Priority: Minor
Right now, there is no way to specify what the start level is for bundles that are found in the auto deploy directory as specified by "felix.auto.deploy.dir" in the felix configuration. By default, it seems that these bundles are always loaded first as compared to other bundles defined in config.properties using the "felix.auto.start.<level>" properties.
Since the shell bundles are in the bundle directory, it would be nice if one could specify that the shell bundles are loaded *after* the application bundles had been loaded, so the shell prompt would show up only then as well, indicating that system startup is complete.
Thus being able to specify a <level> which is related to the <level>s on the "felix.auto.start" property probably makes sense.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2678) Startlevel for bundles in
auto.deploy.dir
Posted by "Tobias Wunden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Wunden closed FELIX-2678.
--------------------------------
The solution works perfectly, thank you Richard for implementing this in express-mode!
> Startlevel for bundles in auto.deploy.dir
> -----------------------------------------
>
> Key: FELIX-2678
> URL: https://issues.apache.org/jira/browse/FELIX-2678
> Project: Felix
> Issue Type: New Feature
> Components: Main
> Affects Versions: framework-3.0.5
> Reporter: Tobias Wunden
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: framework-3.2.0
>
>
> Right now, there is no way to specify what the start level is for bundles that are found in the auto deploy directory as specified by "felix.auto.deploy.dir" in the felix configuration. By default, it seems that these bundles are always loaded first as compared to other bundles defined in config.properties using the "felix.auto.start.<level>" properties.
> Since the shell bundles are in the bundle directory, it would be nice if one could specify that the shell bundles are loaded *after* the application bundles had been loaded, so the shell prompt would show up only then as well, indicating that system startup is complete.
> Thus being able to specify a <level> which is related to the <level>s on the "felix.auto.start" property probably makes sense.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2678) Startlevel for bundles in
auto.deploy.dir
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926727#action_12926727 ]
Richard S. Hall commented on FELIX-2678:
----------------------------------------
To be clear, there is no relationship between when a bundle is loaded and what its start level is. The auto-deploy bundles will still be loaded first, because they are process first. But if we add the ability to set their start level, then they will only start when their appropriate start level is reached, which in your case you could set to be after the auto start property bundles.
> Startlevel for bundles in auto.deploy.dir
> -----------------------------------------
>
> Key: FELIX-2678
> URL: https://issues.apache.org/jira/browse/FELIX-2678
> Project: Felix
> Issue Type: New Feature
> Components: Main
> Affects Versions: framework-3.0.5
> Reporter: Tobias Wunden
> Priority: Minor
>
> Right now, there is no way to specify what the start level is for bundles that are found in the auto deploy directory as specified by "felix.auto.deploy.dir" in the felix configuration. By default, it seems that these bundles are always loaded first as compared to other bundles defined in config.properties using the "felix.auto.start.<level>" properties.
> Since the shell bundles are in the bundle directory, it would be nice if one could specify that the shell bundles are loaded *after* the application bundles had been loaded, so the shell prompt would show up only then as well, indicating that system startup is complete.
> Thus being able to specify a <level> which is related to the <level>s on the "felix.auto.start" property probably makes sense.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2678) Startlevel for bundles in
auto.deploy.dir
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall updated FELIX-2678:
-----------------------------------
Fix Version/s: (was: framework-3.2.0)
framework-3.0.6
> Startlevel for bundles in auto.deploy.dir
> -----------------------------------------
>
> Key: FELIX-2678
> URL: https://issues.apache.org/jira/browse/FELIX-2678
> Project: Felix
> Issue Type: New Feature
> Components: Main
> Affects Versions: framework-3.0.5
> Reporter: Tobias Wunden
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: framework-3.0.6
>
>
> Right now, there is no way to specify what the start level is for bundles that are found in the auto deploy directory as specified by "felix.auto.deploy.dir" in the felix configuration. By default, it seems that these bundles are always loaded first as compared to other bundles defined in config.properties using the "felix.auto.start.<level>" properties.
> Since the shell bundles are in the bundle directory, it would be nice if one could specify that the shell bundles are loaded *after* the application bundles had been loaded, so the shell prompt would show up only then as well, indicating that system startup is complete.
> Thus being able to specify a <level> which is related to the <level>s on the "felix.auto.start" property probably makes sense.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2678) Startlevel for bundles in
auto.deploy.dir
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall updated FELIX-2678:
-----------------------------------
Fix Version/s: framework-3.2.0
> Startlevel for bundles in auto.deploy.dir
> -----------------------------------------
>
> Key: FELIX-2678
> URL: https://issues.apache.org/jira/browse/FELIX-2678
> Project: Felix
> Issue Type: New Feature
> Components: Main
> Affects Versions: framework-3.0.5
> Reporter: Tobias Wunden
> Priority: Minor
> Fix For: framework-3.2.0
>
>
> Right now, there is no way to specify what the start level is for bundles that are found in the auto deploy directory as specified by "felix.auto.deploy.dir" in the felix configuration. By default, it seems that these bundles are always loaded first as compared to other bundles defined in config.properties using the "felix.auto.start.<level>" properties.
> Since the shell bundles are in the bundle directory, it would be nice if one could specify that the shell bundles are loaded *after* the application bundles had been loaded, so the shell prompt would show up only then as well, indicating that system startup is complete.
> Thus being able to specify a <level> which is related to the <level>s on the "felix.auto.start" property probably makes sense.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2678) Startlevel for bundles in
auto.deploy.dir
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall updated FELIX-2678:
-----------------------------------
Component/s: (was: Framework)
Main
> Startlevel for bundles in auto.deploy.dir
> -----------------------------------------
>
> Key: FELIX-2678
> URL: https://issues.apache.org/jira/browse/FELIX-2678
> Project: Felix
> Issue Type: New Feature
> Components: Main
> Affects Versions: framework-3.0.5
> Reporter: Tobias Wunden
> Priority: Minor
>
> Right now, there is no way to specify what the start level is for bundles that are found in the auto deploy directory as specified by "felix.auto.deploy.dir" in the felix configuration. By default, it seems that these bundles are always loaded first as compared to other bundles defined in config.properties using the "felix.auto.start.<level>" properties.
> Since the shell bundles are in the bundle directory, it would be nice if one could specify that the shell bundles are loaded *after* the application bundles had been loaded, so the shell prompt would show up only then as well, indicating that system startup is complete.
> Thus being able to specify a <level> which is related to the <level>s on the "felix.auto.start" property probably makes sense.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2678) Startlevel for bundles in
auto.deploy.dir
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall resolved FELIX-2678.
------------------------------------
Resolution: Fixed
Assignee: Richard S. Hall
I have committed a patch that allows you to specify the start level for bundles in the auto-deploy directory using the felix.auto.deploy.startlevel property. If this property is not set, then the normal initial bundle start level is used, but if it is set, then all bundles in the auto-deploy directory will have their start level set to the specified value (whether they are freshly installed or were installed during a previous framework execution).
Note, if you set this property to a value higher than the framework's beginning start level, then none of the auto-deploy bundles will activate, which typically means you won't be able to interact with the shell.
Please close this issue if you are satisfied, thanks.
> Startlevel for bundles in auto.deploy.dir
> -----------------------------------------
>
> Key: FELIX-2678
> URL: https://issues.apache.org/jira/browse/FELIX-2678
> Project: Felix
> Issue Type: New Feature
> Components: Main
> Affects Versions: framework-3.0.5
> Reporter: Tobias Wunden
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: framework-3.2.0
>
>
> Right now, there is no way to specify what the start level is for bundles that are found in the auto deploy directory as specified by "felix.auto.deploy.dir" in the felix configuration. By default, it seems that these bundles are always loaded first as compared to other bundles defined in config.properties using the "felix.auto.start.<level>" properties.
> Since the shell bundles are in the bundle directory, it would be nice if one could specify that the shell bundles are loaded *after* the application bundles had been loaded, so the shell prompt would show up only then as well, indicating that system startup is complete.
> Thus being able to specify a <level> which is related to the <level>s on the "felix.auto.start" property probably makes sense.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.