Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <356659187.1220026966342.JavaMail.jira@brutus>
Date: Fri, 29 Aug 2008 09:22:46 -0700 (PDT)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Created: (FELIX-705) Consider supporting per-package JAR
 file metadata
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Consider supporting per-package JAR file metadata
-------------------------------------------------

                 Key: FELIX-705
                 URL: https://issues.apache.org/jira/browse/FELIX-705
             Project: Felix
          Issue Type: Improvement
          Components: Framework
    Affects Versions: felix-1.2.0
            Reporter: Richard S. Hall


The JAR spec allows metadata to be specified for packages (e.g., Package.getSpecificationVersion(), etc.). Currently, Felix supports JAR-wide metadata (i.e., the metadata is defined once in the manifest main attributes and is applied to all packages in the JAR file); however, it is also possible to specify per-package metadata. There are some issues in supporting this that need to be considered, such as from where to do the values come (i.e., just the bundle JAR or embedded JARs, etc.) and the impact on performance and memory consumption.

Probably the simplest approach would be to only support metadata in the bundle JAR file itself and not in embedded content or fragments, but is this the correct approach? We need to think about it.

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