Stephen McConnell wrote: > > > Quick glance at the dependency graph: > > sourceresolve dependes on framework 4.1.3 and pool 1.1 > pool 1.1 depends on framework 4.X and excalibur collections 1.0 > excalibur collections is depricated if favout of commons collections > > It would seem to make sense that we update pool to use common > collections, bump pool to 1.2, and validate sourceresolve against > pool 1.2. > Ok.
> A less quick glance at the documentation: > > Tracking down examples of sourcerolve usage is a PITA. The > current documetation basically points you to Cocoon. If you > look around you can find usage in Fortress - but even then, > its somewhat obscure. I think it would much better if the > documentation included some code examples - setting up a > source resolver, adding protocol support, resolving urls, > etc. (including this in the package documentation would be > terrific). > I never got time for this, but I planned it - if someone else wants to do it, fine. > A quick glance at the javadoc: > > Running checkstyle on the code as it would generate lots of > messages about missing @param, @return and @exception > declarations. Are you planning on getting these in? > These will be updated, yes. > A quick glance at the testcases: > > Any plans to get something in place here? > No, not yet. So if anyone wants to do so, he/she is welcome. Carsten -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
