I'm packaging RDT and RadRails for Gentoo Linux, where we build everything from source. It works but I have to make an awkward adjustment to RDT before RadRails will find its classes. When Eclipse plugins started being packed into singular JARs, most stored their classes directly within that JAR but for some reason, RDT stores its classes within a nested JAR. This should be a problem for the headless PDE because it works fine at runtime but since RDT is the only plugin I know of that does this, I figured I'd report this here. It just involves making a couple of changes to build.properties and MANIFEST.MF. Taking org.epic.regexp as an example... build.properties BEFORE: source.regexp.jar = src/ bin.includes = plugin.xml,\ *.jar,\ regexp.jar,\ shortcuts,\ icons/,\ META-INF/ build.properties AFTER: source.. = src/ output.. = bin/ bin.includes = plugin.xml,\ *.jar,\ .,\ shortcuts,\ icons/,\ META-INF/ MANIFEST.MF BEFORE: ... Bundle-ClassPath: regexp.jar, gnu-regexp-1.1.4.jar ... MANIFEST.MF AFTER: ... Bundle-ClassPath: ., gnu-regexp-1.1.4.jar ... Where there are no dependency JARs, you can remove the Bundle-ClassPath entry altogether. Having the dependency JARs nested isn't a problem for me because we source these externally anyway. I suspect you won't edit the files by hand but I've never written a plugin, I just build the things! I might be able to return the favour. If it's of any use to you, I have patches for RDT to make it build with Eclipse 3.3 and JRuby 1.1.2, though I suspect you've got 3.3 covered already. Let me know and I'll make another ticket.