Actually, I have seen Jdepend before. It does metrics from what I understand and I am trying to have the build fail when the package design is violated...ie. the developer must change the design or must make code changes to adhere better to the current design.....ie. it forces the developer to consciously think about design changes when he makes changes without realizing it affected the design....you can actually make a design so the controller depends on the view and model so if someone actually adds code in the model package that depends on the view package, the build will fail and tell them the design does not allow this...change the design or the code(and in this case preferably the code) Thanks, dean
-----Original Message----- From: Kees Jan Koster [mailto:[EMAIL PROTECTED] Sent: Sunday, January 02, 2005 12:48 PM To: BCEL Users List Subject: Re: newb: How to determine package dependencies from one jar? Dear Dean, > > Is there a way to use the bcel, to go through a jar and determine that > biz.xsoftware.router depends on biz.xsoftware.model? I basically want > to go through all the class files in biz.xosftware.router package and > see if any depend on any classes in the bix.xsoftware.model. > For this particular purpose, perhaps you could consider using JDepend? http://www.clarkware.com/software/JDepend.html Of course, if this is an excercise to learn how to use BCEL, ignore this message. :-) Kees Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
