Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <826695914.1237895273358.JavaMail.jira@brutus>
Date: Tue, 24 Mar 2009 04:47:53 -0700 (PDT)
From: "Sahoo (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-932) Don't install plain jar files as
 bundles
In-Reply-To: <337775536.1234255139956.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688652#action_12688652 ] 

Sahoo commented on FELIX-932:
-----------------------------

[I wanted to add this comment while closing the issue, but there was a minor glitch while closing, so I could not add the comment then. Adding it now]

Given that it is not easy to find out whether a jar is bundle or not, and there is no side effect of installing a plain jar as a bundle, I am fine with the current behavior. So, I am closing the issue as INVALID.

> Don't install plain jar files as bundles
> ----------------------------------------
>
>                 Key: FELIX-932
>                 URL: https://issues.apache.org/jira/browse/FELIX-932
>             Project: Felix
>          Issue Type: Bug
>          Components: File Install
>         Environment: generic
>            Reporter: Sahoo
>
> File Install bundle currently does not check the jar file to see if it has any OSGi metadata or not. It assumes every jar file as OSGi bundle and installs them. At the minimum, it should look for Bundle-SymbolicName header and in the absence of the same, it should exclude the jar file.

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