[jboss-osgi-issues] [JBoss JIRA] Resolved: (JBOSGI-345) Support specifying start levels for bundles deployed in the deploy directory
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Tue Jul 26 05:53:26 EDT 2011
[ https://issues.jboss.org/browse/JBOSGI-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler resolved JBOSGI-345.
-----------------------------------
Resolution: Out of Date
Out of Date
> Support specifying start levels for bundles deployed in the deploy directory
> ----------------------------------------------------------------------------
>
> Key: JBOSGI-345
> URL: https://issues.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
> Priority: Minor
> Fix For: Approved and Unscheduled
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-osgi-issues
mailing list