Because every dependency is just that: a dependency. Extra complexity is bad. "Installing a package" sounds simple, and IMO should be simple; if "installing webwork" is actually "installing webwork, xwork, commons-logging, ognl, then configuring, then writing actions, then debugging" there's a considerable barrier to using webwork. This is, in fact, the real process... and luckily, the LAST step isn't that bad because webwork's pretty dadgummed simple.
Most people are USED to lots and lots of dependencies, and are just now discovering things like: xerces wasn't such a wonderful idea, as the version they used isn't working with the version someone else used... what fun. (Truth: the project I'm on in my day job actually requires two versions of xerces in the classpath.) Now, SURELY depending on Jelly won't make that happen, right? Sorry; I'm a bit too much of a skeptic to think so. Adding an optional dependency is fine... if people decide they can't use whatever version of Jelly you have or need, they just ... don't use its features. No big deal. Adding a real dependency needs to be a matter of "Do we *really* need this? Are we going to see some serious benefits?" Look at how the Velocity dependency was decided: "We will suggest it. If you don't have it, your UI tag includes will fall back to JSP." That's an optional dependency, and if you've written eight billion pages that use Velocity 1.1 and WW uses Velocity 1.3b... you're still in good shape. (Yes, I'm ignoring the fact that WW 2.0 probably won't be compatible with those eight billion pages.) So what does Jelly add that is such an incredible benefit that the entire project's userbase has to use it? Why hasn't the need exposed itself already? On Sat, 8 Feb 2003, Kelvin Tan wrote: > Care to elaborate on why you think so? > > On Fri, 7 Feb 2003 03:40:57 -0500 (EST), Joseph Ottinger said: > >Depends on the use. I don't think there'd be a problem eventually > >allowing Jelly's use, but depending on Jelly would be a Bad Thing. > > > >On Fri, 7 Feb 2003, Kelvin Tan wrote: > > > >>Did a search in the archives and didn't find anything noteworthy > >>re: WW + Jelly, so thought I'd bring it up. > >> > >>Has this been discussed before? Perhaps not just using it as > >>"another view", but in a more integrated fashion, ala OGNL and the > >>current EL? > >>After all, Jelly has a large collection of existing taglibs, and > >>support for JEXL... > >> > >>Regards, Kelvin > >> > >>-------- > >>The book giving manifesto - http://how.to/sharethisbook > >> > >> > >> > >> > >>------------------------------------------------------- > >>This SF.NET email is sponsored by: SourceForge Enterprise Edition + > >>IBM + LinuxWorld http://www.vasoftware.com > >>_______________________________________________ Opensymphony- > >>webwork mailing list [EMAIL PROTECTED] > >>https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > >> > > > >--------------------------------------------------------- > >Joseph B. Ottinger [EMAIL PROTECTED] > >http://enigmastation.com IT Consultant > > > > > > > >------------------------------------------------------- > >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 http://www.vasoftware.com > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > --------------------------------------------------------- Joseph B. Ottinger [EMAIL PROTECTED] http://enigmastation.com IT Consultant ------------------------------------------------------- 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
