Tom Morris wrote: > You're probably get more useful feedback if you provided pointers to > exactly what you're looking at when you say "build system" and how you > define "size and complexity." In addition to Bob's suggestion of the > removal of unused components, another possibility that comes to mind > is that things could have been reorganized among the various > subprojects and you're not looking at all of them. > Thanks for the suggestions, Tom. Below is some clarification of the terms I used:
Build System: The system exercised to produce the ArgoUML deliverables from the source code. That is, build.sh and all ANT build code it executes. Build System Size: Defined in terms of number of files, number of targets, number of tasks, and lines of code in the build system. Build System Complexity: Measured using Halstead complexity metrics (Volume, Difficulty, Effort) and some runtime build graph measurements of the default ArgoUML build. These include the length (number of targets or tasks hit) and the depth (maximum depth of recursion). In terms of my methodology for gathering the build sources, it may be possible that I've overlooked some files. I considered all "build.xml" files found and manually checked the other "*.xml" files in the source snapshots of each release. Properties files were excluded from consideration. If there are any files I may not have considered, please let me know. ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2432052 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
