> >I'm not sure, but you might be able to use the >ClassLoader and reflection to achieve this although I >suppose you'll want this info before run-time. OTOH, >in order to build a set of classes used by the >application (and not have any false negatives), using >the ClassLoader will give you exactly that set. >
Im interested this but not sure how to go about it. can you give me a few pointers Id want to get the info on calling the main with a -version param >From experience, if you do it the way you want, you'll >have to contend with a lot of version-to-version >dependency issues (eg which versions of class X will >work with which versions of class Y?). It's much >easier to deal with these issues from a larger-grained >perspective (eg which versions of >component/package/module X will work with which >versions of component/package/module Y). the problem is that I have loads of classes in many different packages each applications individual classes are in a seperate package but they use many of the same util classes I often update my util classes, always keeping the same interfaces, but mabe adding others. If I update one of these I do not want to put a new 'tag' on the applications that use it for many reasons: 1: It wont change the application 2: I would have to look at every class in every application to see if it used the util class, and so then update it with a new tag or not 3: would not the util class have to have a different tag for each application that used it?(they might start stacking up) 4: all my applications are packaged in one jar and so will use the util class there not just the one when the application was last 'tagged' _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
