Hani Suleiman 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.
Yes, it exists. JBoss people produces an external module to deal with
MBeans interface generation. Similar to the generic JMX module, but
specific to JBoss.
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.
The initial motivation for the 1.2 series was modularization. Of course
we did far more than that, but it's silly to change back to a single
codebase now.
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.
Yes, but if you just want to generate a generic web.xml you don't need
jboss or weblogic.
We *could* separate the jboss plugins into jboss-ejb and jboss-web, for
example, so you don't have to use the web module if you just want
jboss+ejb, but decided that we don't need that much modularizaton. But
the framework for this is in place, and we could change this at any time.
And one last word: I agree with Aslak. What's wrong with <fileset
dir="${xdoclet.dir}" includes="*.jar"/>?
--
Marcus Brito <[EMAIL PROTECTED]>
-------------------------------------------------------
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
