You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org> on 2011/11/20 22:53:52 UTC

[jira] [Closed] (KARAF-380) Add .jar deployer autowrapping non-bundle-jar files dropped to deploy folder

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

Jamie goodyear closed KARAF-380.
--------------------------------

    
> 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 ordered.
> And checking the 'jar' extension would clearly remove most of the bad situations for that case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira