Hi, I pushed a first round of refactoring and I would like to continue but before that happens I'm going to take the checkstyle violations down to zero, add the clover report, get the test coverage up to 100%, and start adding extensively to the touchstone build.
The other area of concern is some sort of test harness for the jelly portions of Maven so JellyUnit is probably a good idea. Maybe someone could devise a method of measuring coverage in Jelly scripts :-) Once the checkstyle violations are out of the way and the test coverage approaches something more reasonable (currently it's at 20% which isn't something reasonable if we expect maven to be reliable) then I will be much happier allowing fundamental changes in the core. Also at that point, changes and patches will not be accepted without the accompanying adherence to checkstyle properties and appropriate test coverage. I am to blame for not maintaining the levels that are necessary if Maven is to be a truly useful tool so I will try and correct these things this week. Once checkstyle and testing is taken care of I will add test builds and then refactor again for inheritance. On another note Brian Leonard sent in some patches to make the JXR report much more navigable and generally more attractive. Many thanks! -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
