On 12/17/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > 2007/12/17, Don Brown <[EMAIL PROTECTED]>: > > Hmm...this is kinda a bigger issue - should our assembly contain all > > the files for the frameworks that the plugin provides support for? We > > don't include every Spring jar or a JSF framework with our JSF plugin. > > I'd lean towards not including jars we don't have to - our downloads > > are big enough (some would say 100 megs for a web framework with 2 > > real dependencies is a bit overkill). > > I don't think that Tiles is a "bigger" issue: The S2/T2 plugin has a compile > dependency on tiles-core (that, in turn, depends on tiles-api), but > tiles-jsp is necessary for a typical use.
My preference is to ship only the minimal amount of jars, but in true open source fashion, you are the one that maintains the Tiles plugin, so it is your call. That inclusion should happen at the plugin build level, though, to keep all the tiles dep info in one place. I've added the retrotranslator runtime jars back into the appropriate assemblies. Let me know if there are any other missing jars, or better yet, add them in yourself :) Don --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
