Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: felix-dev@incubator.apache.org
Message-ID: <22787258.1171322585858.JavaMail.jira@brutus>
Date: Mon, 12 Feb 2007 15:23:05 -0800 (PST)
From: "Karl Pauls (JIRA)" <jira@apache.org>
To: felix-dev@incubator.apache.org
Subject: [jira] Assigned: (FELIX-30) Implement extension bundles
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/FELIX-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls reassigned FELIX-30:
-------------------------------

    Assignee: Karl Pauls

> Implement extension bundles
> ---------------------------
>
>                 Key: FELIX-30
>                 URL: https://issues.apache.org/jira/browse/FELIX-30
>             Project: Felix
>          Issue Type: New Feature
>          Components: Framework, Specification compliance
>            Reporter: Richard S. Hall
>         Assigned To: Karl Pauls
>            Priority: Minor
>
> This issue is described in section 3.15 of the OSGi R4 specification. The main jist is to provide a standard mechanism to place classes on the JVM boot class path and to deliver framework extensions and/or updates. This mechanisms is modeled as bundle fragments, but it not really completely related to it. The boot class path aspect is likely to be dependent on specific JVMs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.