Hi,
+1
> +1 to removing mx4j from xdoclet's build, because:
> - it doesn't seem to be generic enough
> - and btw do we need it in the core?
>
> I think we definitely need to follow the path ant follows:
> - a core (xdoclet core + core tasks/subtasks)
EJB, Web, MBean
> - a set of optional tasks/subtasks
> - a separate xdoclet-contrib module for special purpose items
Here is separation is not clear to me
Is it:
optional : dataobject, valueobject, util, dao
contrib : mx4j, webwork/struts, jboss/weblogic/mvcsoft
Core+Optional release every month (strong, solid, unit tested,
blablabla)
contrib release every week ("the right relationship in jboss v3 is
wrong in case ...")
Is that the idea ?
>
> Ara.
>
Vincent
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
