On 12/17/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > The Struts 2/Tiles 2 plugin does not depend on tiles-jsp, so I suppose that > it isn't there...
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). > BTW, I noticed that you removed the backport-utils and > retrotranslator-runtime dependencies: are they still there in backport > assemblies? (Sorry for the question but at the moment I cannot test myself). I had thought they were included in the jars, but looking at them again, I see the size increase isn't large enough. I'll put those back in. > I don't like the approach. I think it is best to create assemblies on your > local machine by removing all the unneeded dependencies to clean up the pom > and the assembly descriptors, until the assemblies are exactly the same as > they were before your intervention. > After that, we could discuss the removal of dependencies and jars from the > distributions. Fair enough, I guess we prefer different approaches here. Since the assembly didn't work before, it is hard to compare, but I pulled down 2.0.11 so I'll use that. Still, as it sits now, even our slimmed down lib zip is 59 megs, so I think we need to get serious about cutting the fat. Don > > Thanks > Antonio > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
