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

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.0
• Assignee: Jean-Baptiste Onofré
• Reporter: Andreas Pieber
• Created: 11/Jan/11 13:59
• Updated: 02/May/13 02:28
• Resolved: 27/Jan/11 09:59

Description

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.

Issue Links

• depends upon: FELIX-2798 ArtifactListener services are not ordered according to the OSGi ranking