Splitting up sablevm-classpath into separate packages

Hi,

sablevm-classpath has grown quite a bit in size since 1.1.6.

Available disk (flash actually) space is limited on handheld
devices, so I wonder how to split up sablevm-classpath into
separate packages for the familiar 0.8 release.

The idea is to package optional classes separately, so that
users will only have to install what they really need.

I am now seeking advice on how to achieve this in a way that
is most likely to suit the needs of different types of
applications.

I imagine packaging javax.* and java.awt.* separately might
be a start. However, packaging each java package separately
might be overkill...

What do you think?

Regards,

Rene

PS: Each package will provide an individual .jar. I'm not sure
about the disk usage or performance impact yet...