You may find it useful with XDoclet to have a big patchfile to apply whenever you checkout XDoclet, as the committers do not seem to get much time for applying patches
I'll speak for myself here since I might be the most savvy (ex!) Struts committer. I'm weary of apply patches that do not directly relate to our usage patterns that I can easily test. For example, I don't use XDoclet-generated action mappings, rather I use a merge file for these.
I understand users frustrations with broken open source software though. I've been there myself and in fact I'm routinely there and often have to resort stepping up to the plate myself and fix things locally and then make a lot of noise in the community until the fixes are applied (or to shut me up they make me a committer to fix it myself :).
I'm not sure what the lifespan of XDoclet 1.x is at this point, but I'm currently in a wait-and-see mode with it. XDoclet 1.2 is doing everything we need it to do quite well at the moment so I'm not eager to apply patches. XDoclet2 is around the corner, so pragmatically my next move may be to shift entirely to that camp.
Perhaps you'd be interested in being a 1.x codebase committer, Matt? If so, keep bugging us and pointing us to your patches and we can bring up a vote.
Erik
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
