Hi guys. Here are my EUR 0.02.
I think jakarta is a good place, since xdoclet is bundled pretty tight with other jakarta products. It relies on ant, and will rely on velocity and BCEL soon. It produces a lot of usefull stuff for other jakarta projects ( i.e. struts ) Other jakarta projects can benefit from code generation in future. I can not imagine all the ways to "abuse" xdoclet. If it can be generated based on formal javadoc-like tags - xdoclet does it. So we already have tight relationship with jakarta ( though not everybody at jakarta may know it :) ), and moving there would be logical. I'm not sure if jakarta support is better than sourceforge, but at least it would be easier to speak to them as to sourceforge (on SF there are shitload of pprojects, on jakarta far less) Another issue is "coolness" - jakarta is well known and has a good name. Being there would make lobbying xdoclet to projects in real world easier ( though I had no problem to lobby xdoclet, after I have shown what it does. There is usually no discussion after this point ) So my decision is +1. After modularized version is released. regards, ===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
