Geir Magnusson Jr wrote: > does it make sense to move the launcher there? We'll need to reuse for > other tools.
I don't think so. The tools should be capable of being written in Java code, so putting all that logic under enhanced/tools/javadoc or whatever makes sense, and creating a common tools framework in Java; but the launcher has a closer affinity to the class lib code than a general tool would be expected to have (it has to set up the portlib, VMI interface to the VM, create the VM etc.). I can imaging that we put code in the launcher to make it invoke a tool trivially in the tools framework, but that would be a specialization of the generic launcher. Regards, Tim > Geir Magnusson Jr wrote: >> Where do you think we should put this? It doesn't belong in classlib. >> >> I'm going to make a tools subproject that's a peer to classlib to try >> and get people working on our toolset. >> >> Think it should go in there? >> >> > -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK.
