Dennis,Jelly is something that strives to do lots of things so it is understandable that it has a lot of "dependencies" but a lot of them is purpose specific. For example there may be a dependency on xalan of the XML tag-library but that would only be for JDK < 1.4 and only for the usage of the transform tag. If you're not using it... remove it ! Jaxen is another example of a multi-purpose library whose dependency on dom4j is only if you use dom4j (which jelly does), on jdom only if with jdom etc... and, I think, has no reason to depend on xalan if not doing transformations.
Splitting in extra modules is not very doable to me... There will always be "features" of some modules that you will want to ignore hence the recursive dependencies of maven (are you using this?) fails unless purposes of dependencies can be encoded.
Does it help ? paul Dennis Kempin wrote:
i integrated jelly into a framework project of mine as some kind of templatelanguage which works really great!I am using maven and wondered why my example.war file had about 12MB in theWEB-INF/libs directory. Most space is taken by the jaxen dependency, which depends in xalan which has 3MB. I browsed the jelly code and just wanted to know if it would bepossible to exclude some dependencies, maybe by splitting up some featuresinto extra modules.
smime.p7s
Description: S/MIME Cryptographic Signature
