Jason Carreira wrote:
Yup. I have no issue with adding build targets that build the above specific stuff, but separating it into separate CVS modules just brings more headache than it's worth.So the real question here is whether it makes sense to partition Webwork 2.0 into:Webwork-core Webwork-el Webwork-jsp Webwork-velocity Webwork-xslt Webwork-jasperreports Webwork-freemarket There may be later extensions to Xwork as well (JMSWork?, MailWork?). Personally, I think Webwork is small enough to stand as one module with all of the view types included.
/Rickard
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
