[Not that I'll have time over the next few days, but maybe within the next week, but ...] I'd like to work towards getting some things built w/ Gump3, by working on two plug-ins, (or one with two modes). The first will "lay out the plan", constructing classpaths and such, and recording these decisions onto the model. This could be a pre-process visitor. The second will leverage that information in order to perform the build (a process visitor.)
The reason for the split (if not obvious) would be that we can view/test the "build plan" w/o having to run it. Also, it ought be easier to handle cases where we wish to "copy the jars from that project", but then "break" dependency links. Splitting this into two ought allow us more flexibility. Seem about right? regards, Adam P.S. Sooner or later I'll just commit something, honest. ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
