Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@karaf.apache.org
Message-ID: <8678806.345621294936789457.JavaMail.jira@thor>
Date: Thu, 13 Jan 2011 11:39:49 -0500 (EST)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Subject: [jira] Commented: (KARAF-380) Add .jar deployer autowrapping
 non-bundle-jar files dropped to deploy folder
In-Reply-To: <24267172.282271294754453763.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-380?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12981=
324#action_12981324 ]=20

Jean-Baptiste Onofr=C3=A9 commented on KARAF-380:
--------------------------------------------

It's a good idea Andreas.

The PAX URL wrap: protocol provides the possibility to define OSGi statemen=
t in the URI (such as the Bundle-SymbolicName, etc).
What do you think to add a .osgi file near the .jar file describing the OSG=
i statements, like:

my.jar
my.osgi

where my.osgi contains:

Bundle-SymbolicName:
Bundle-Version:

etc ?

> Add .jar deployer autowrapping non-bundle-jar files dropped to deploy fol=
der
> -------------------------------------------------------------------------=
---
>
>                 Key: KARAF-380
>                 URL: https://issues.apache.org/jira/browse/KARAF-380
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Andreas Pieber
>
> See http://mail-archives.apache.org/mod_mbox/karaf-dev/201101.mbox/browse=
r for full discussion; short summary:
> My concern is to deploy clients JARs like by example JARS used by project=
 Apache Hadoop
> If we detect a file in the deploy/ directory with the extension '.jar', A=
ND the JAR's manifest does NOT contain any OSGi headers, THEN we assume tha=
t it's a plain-old-jar, and perform an auto-wrap.
> Using the OSGi ranking attribute on services should be sufficient in orde=
r to keep them ordered.
> And checking the 'jar' extension would clearly remove most of the bad sit=
uations for that case.

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