[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-345) Support specifying start levels for bundles deployed in the deploy directory

[Thomas Diesler (JIRA)]

     [ https://jira.jboss.org/browse/JBOSGI-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler updated JBOSGI-345:
----------------------------------

    Fix Version/s:  JBossOSGi 1.0.x


> Support specifying start levels for bundles deployed in the deploy directory
> ----------------------------------------------------------------------------
>
>                 Key: JBOSGI-345
>                 URL: https://jira.jboss.org/browse/JBOSGI-345
>             Project: JBoss OSGi
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Core Framework
>    Affects Versions: JBossOSGi 1.0.0 Beta7
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>             Fix For:  JBossOSGi 1.0.x
>
>
> When deloying bundles by placing them in the deploy directory it should be possible to specify their start level and whether they need to be started or just installed. 
> One idea is to start supporting 'companion' files that have the same name as the bundle but then with a different extension. So information like this could be placed in a myBundle.md file for a bundle called myBundle.jar. The .md file would be placed in the deploy directory as well and needs to be there before the bundle.
> Another note is that this mechanism should also work when JBosgi is run in AS

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira