Thanks for the info. Your solution of having all the base code in an external library is where I started out, but I wasn't entirely comfortable having all the core code in an RSL (I don't exactly remember why that bothered me so much now). It certainly makes maintenance and development alot easier instead of having to manage a pile of Interfaces and Abstract classes in addition to everything else.
Derrick --- In [email protected], EECOLOR <[EMAIL PROTECTED]> wrote: > > Hello, > > the way we handle this is as follows: > > We have one library swc that holds our code base. We have an application > file that contains all basic application code. This application is compiled > with the option -link-report=linkreport.xml. All separate modules are > compiled with the option -load-externs, this option allows you to have the > required classes in your classpath for type checking, but leaves all > available classes out (the ones in the basic application). > > > Greetz Erik > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
