karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Pieber (JIRA)" <j...@apache.org>
Subject [jira] Created: (KARAF-380) Add .jar deployer autowrapping non-bundle-jar files dropped to deploy folder
Date Tue, 11 Jan 2011 14:00:53 GMT
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


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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message