Re: [OS-webwork] Partition XWork [Was: Re: XWork flux]

[Hani Suleiman]

-1 from me, I like that it's one nice webwork.jar to plop in. Having to pay another 30k for velocity support (or whatever else I don't use currently) isn't such a big deal. It's too jakartaish to have your product be 50 jars.

On Thursday, January 30, 2003, at 01:15 PM, Rickard �berg wrote:

Jason Carreira wrote:

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.

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.

/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

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