karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (KARAF-380) Add .jar deployer autowrapping non-bundle-jar files dropped to deploy folder
Date Thu, 27 Jan 2011 09:59:45 GMT

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

Guillaume Nodet resolved KARAF-380.

       Resolution: Fixed
    Fix Version/s: 2.2.0

I think this one is done now.

> Add .jar deployer autowrapping non-bundle-jar files dropped to deploy folder
> ----------------------------------------------------------------------------
>                 Key: KARAF-380
>                 URL: https://issues.apache.org/jira/browse/KARAF-380
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Andreas Pieber
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.2.0
> See http://mail-archives.apache.org/mod_mbox/karaf-dev/201101.mbox/browser 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', AND the JAR's
manifest does NOT contain any OSGi headers, THEN we assume that it's a plain-old-jar, and
perform an auto-wrap.
> Using the OSGi ranking attribute on services should be sufficient in order to keep them
> And checking the 'jar' extension would clearly remove most of the bad situations for
that case.

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

View raw message