Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Tue, 20 Sep 2011 19:44:08 +0000 (UTC)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: 
 <1539489015.47428.1316547848811.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <569777582.10260.1305298247452.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (FELIX-2950) [Framework] Adopt OSGi R4.3 API as
 framework internal API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Richard S. Hall closed FELIX-2950.
----------------------------------

    Resolution: Fixed

For the most part, this is done, so I'm closing this bug.

> [Framework] Adopt OSGi R4.3 API as framework internal API
> ---------------------------------------------------------
>
>                 Key: FELIX-2950
>                 URL: https://issues.apache.org/jira/browse/FELIX-2950
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework, Specification compliance
>    Affects Versions: framework-3.2.2
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: framework-4.0.0
>
>
> The R4.3 specification introduces more detailed API modeling bundle revisions and wiring. Rather than just facading our existing abstractions for these concepts, we should modify the framework implementation to adopt them wholesale (i.e., replace our existing abstractions with the spec'ed abstractions). Although the standard abstractions do not map one-to-one with our existing abstractions, they are reasonably close and the benefit of having an implementation that is consistent with the standard API probably outweighs the cost of changing, since very few people actually depend on our internal API.
> This issue will only be used for this internal refactoring process and generally will not be used as the issue for implementing new R4.3 functionality. We'll try to introduce separate issues for new any new functionality to make the change log more meaningful.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira