Just to play the devil's advocate...

On Tuesday, February 11, 2003, at 07:35 PM, Aslak Hellesoy wrote:

1) It makes it easier for us to encourage people to build and maintain
plugins outside the XDoclet codebase.
Does this exist anywhere? As far as I know all plugins are in the xdoclet codebase.

2) It simplifies the build process. (It's already too complicated).
I'm sure that if it all becomes one codebase, it'd certainly be quite easy to have a not so complex build process. It's not an impossible task anyway.

3) It avoids dealing with one potentially very big jar. Well, 2 MB isn't
actually gigantesque, but it's big.

Sure, except that it's starting to feel like jakarta commons, where they're all one big incestuous family and if you want to use any of the newer commons jars, you have to bring in 4 other jars. It's hugely irritating. The equivalent in xdoclet is that to use jboss module, you have to have web module (even if you don't use any web features), and jmx. If you want to use weblogic (again, no web stuff), you need web module. The modular approach works if there are no cross-module dependencies. As things stand, if someone wants to deploy ejbs to jboss, they need 6 jars (xjavadoc, xdoclet, jboss, jmx, web, and ejb), which to me doesn't feel very modular.



-------------------------------------------------------
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

Reply via email to