Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 98374 invoked from network); 2 Feb 2002 14:36:15 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Feb 2002 14:36:15 -0000 Received: (qmail 21225 invoked by uid 97); 2 Feb 2002 14:36:14 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 21191 invoked by uid 97); 2 Feb 2002 14:36:13 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 21180 invoked from network); 2 Feb 2002 14:36:13 -0000 Message-Id: <200202021436.g12EaA813952@mail008.syd.optusnet.com.au> Content-Type: text/plain; charset="iso-8859-1" From: Peter Donald To: ant-dev@jakarta.apache.org Subject: JDepend Date: Sun, 3 Feb 2002 01:32:24 +1100 X-Mailer: KMail [version 1.3.2] X-Wisdom-Cookie: . MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I have setup a basic jdepend task and report (dependency information about codebase) for the main ant tree. However it turns out that it points out more problem areas in the main ant codebase (ie circular dependencies and very very very scattered interactions and so forth) and since we can't change it - it doesn't seem to be a good idea of reporting it everyday? Or maybe not - what do you think? Should I commit it or not. It would also mean that we need to include jdepend 2.1+ in CVS. In myrmidon I actually integrated it into JUnit tests. So I make sure that; * the org.apache.aut.* tree does not have any dependencies on the rest of the codebase * the launcher does not have references to any other ant class * that the implementations of the container interfaces are not directly referred to by anything other than those classes in same package * there are no circular dependencies In time I will also do things that make sure that the antlibs dont refer to other antlibs and make sure that the efferent connections (ie what the package depends upon) are within tolerable proportions, and whether the "Distance from the Main Sequence" (or makeup of classes) is of an acceptable value. -- Cheers, Pete --------------------------------------------------- "Wise men don't need advice. Fools don't take it." -Benjamin Franklin --------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: