I would like to see a modularization of the Java libraries. This will allow for use of Java/gcj in an embedded or semi-embedded environment with the benefits of a "full" java. However - it shall still be possible to build a single module too for those environments that doesn't need modularization. I understand that this is no easy task due to cross-depenencies.
Confirmed, I thought I saw this somewhere else.
Created attachment 10237 [details] Proposal for the initial split. This is the initial split I did, and I must admit that it isn't thoroughly tested. There are one text file for each module I created. The text file contains an initial dependency description and a list of files incorporated in that module. In addition to this there is one Java-file with code modified to dynamically load the DefaultContentHandlerFactory that now resides in the AWT package from the URLConnection class. This wasn't necessary earlier. Beware that this is completely untested and I see it as a proposed modification. I REALLY wanted to break out the security classes too, since they have a significant size and aren't really needed on an embedded system. This is my minimal effort breakup - it could have been even better.
Closing as won't fix as libgcj (and the java front-end) has been removed from the trunk.