Based on http://mime-util.svn.sourceforge.net/viewvc/mime-util/trunk/eu.medsea.mimeutil/src/eu/medsea/mimeutil/magicfile/Helper.java?revision=91&view=markup, the magic.mime file has to be in the root of the classpath, not META-INF.
Are you embedding mime-util into your own bundle or using it as a separate bundle? In the latter case, I think you'll have to use the system property/file system mechanism. In the former case, it should work. In general, if you're using maven-bundle-plugin, you shouldn't be mucking with Bundle-Classpath too much. m-b-p will manage it for you. You might want to try Tika instead. I know they're OSGi-friendly :) Justin On 9/29/10 1:09 PM, mvangeert...@comcast.net wrote: > > > All, > > > > I'm not sure if this is an OSGi issue or an issue with the source-forge > mime-utility, but I'll ask here because the Mime-utility's forum is fairly > dead. > > > > the Mime utility requires a file called magic.mime to be located in the > classpath. Currently, I have that file located in META-INF, but honestly, > I've tried putting it in about a dozen places. When setting my > bundle-classpath to META-INF/magic.mime, and when not having a > bundle-classpath at all, the bundle is unable to find the file. Has anyone > experienced this issue, and/or do any of you have an idea what the problem > could be? > > > > v/r, > > > > Mike Van > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
