Michael McGrady wrote:
What I suggested was putting in JavaSpaces all the interfaces that are
part of the JavaSpaces functionality.
So, if all I need to do in a Java program is
public class MyClass {
public static void main( String args[] ) {
System.out.println("You won the lotto!");
}
}
that I should be able to convince Sun that they should have a version of the JDK
that I can download that just supports String and System and no other classes
because I don't need them?
Do you ever pick jars apart and reassemble their contents into something that
has just what you need? Do you build your -dl.jar files with classdepandjar so
that only what you need is included in the download?
I guess I see the use of unjar and jar tasks and classdepandjar in my ant
scripts as the packaging solution that works reliably for me to just have what I
am using. Do you think this doesn't solve the problem (you stated too many
unused classes that you have to "inspect", I believe, as one of the driving forces)?
Gregg Wonderly
