Hi, I think the problem is a little bit more complex. The problem I see with external module maintainers is that first, there is no offical module for an app-server, and second how would you drive cross-modules functionnalities (like the @ejb javadoc space?).
For the first issue, I think that the XDoclet2 team should indicate which module is the "offical" one and list it on the website. It would "defend" this module and change its position only if the implementation is not maintained anymore. This should drive forces toward a good "reference" module. For the second issue, having the first one solved would help this as the various module implementors would simply have to communicate between them. The result (I mean the cross-modules tags) would then end up published on the XDoclet2 site. Any thoughts? Jerome. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
