In message: <[EMAIL PROTECTED]> Andrew Pimlott <[EMAIL PROTECTED]> writes: >On Sat, May 18, 2002 at 10:53:29AM -0700, T. Alexander Popiel wrote: >> 5. Would it be useful to folks if I made available a second dh_java* >> tool for taking a list of entry-point .classes and putting them >> (and all the .classes they depended on, excluding ones already >> in indicated .jars) into a .jar file? (This is actually one of >> the functions of the tool that I'm munging to make dh_javadeps... >> and I personally find it quite useful for making minimal .jars >> out of a source tree containing multiple related programs.) > >I don't have any opinion on this, but make it clear that it can't >work reliably in the presence of reflection. Bonus points if you >give users a way to specify classes that are required by reflection.
Not just reflection; any case where a class is loaded by non-standard means. (I do this a lot, actually, particularly with gui layouts.) Yes, the tool can take a list of classes that must be included; not all of them have to be actual entry points. - Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
