[02:11] <persia> jpds, Ideally, you want to build everything at build-time on the buildds.  There's three ways to work around the sort of issue you've described.  First is to build Installer.class at build-time, and use that to do the install (or package whatever does the install separately, and use that).  The second is use javahelper to work around the upstream build system.  The third is to use dh_install to put things somewhere, and then mangle them after t
[02:11] <persia> he dh_install run into that which you want.
[02:18] <persia> Actually, thinking about it, there's a fourth option, which would be to just build the package basically manually in your install rule.
[11:23] <jpds> persia: Hmm, it seems all that the graphical Installer.class program does is uncompress the 'bluej-dist.jar' to an install directory - so I guess I'll just dh_install those :)
[11:29] <persia> jpds, You might want to read some of the javahelper docs: there's stuff in place that can execute from the uncompressed jar.
[11:30] <persia> And yeah, if it's graphical, it's just painful to build-dep on an X emulator.
[11:33] <jpds> I'll take a look at javahelper, thanks.
[11:34] <persia> You'll need to add special information to the jar, but it ought make it easier to just dump a jar in /usr/lib/java and a symlink in /usr/bin than worry about all the .class files.