Hah! Well, you might want to hold off on that, as I took a different approach to the velocity issue -- I joined the project and am working on a new release :)
And we do always have the option of using the velocity release that internalizes all dependencies so that it has no external dependencies. I'll have to look at these again, but I think it packages them. On Fri, Jun 12, 2015 at 10:34 AM, Andrus Adamchik <and...@objectstyle.org> wrote: > (taking to dev) > > Yeah, Velocity is the dirtiest of the remaining Cayenne dependencies that > drags a bunch of other things into the stack. > > I am thinking of creating a pluggable syntax for SQLTemplate. By default > Cayenne would provide a simple parser that is a subset of Velocity, but > without Velocity (support for $var variables, #bind, #result and other > Cayenne directives). And moving full Velocity integration into a separate > module to avoid the dependency tail. > > Andrus > >> On Jun 12, 2015, at 5:27 PM, Mike Kienenberger <mkien...@gmail.com> wrote: >> >> On Fri, Jun 12, 2015 at 10:20 AM, Andrew Willerding >> <awillerd...@itsurcom.com> wrote: >>>> Which commons lang version? >>> >>> I'm including the one bundled with Cayenne - commons-collections-3.2.1 >> >> That's not a commons-lang library. That's commons-collections. >> >> I took a quick peek at the cayenne binary distribution, and we do not >> distribute commons-lang. >> >> The version of velocity distributed is 1.6.3. >> >> The dependency there is: >> >> jar.commons-lang.version= 2.4 >> >> So you will need 2.4, 2.5, or 2.6 (2.4 is the safest if you have no >> other commons-lang 2.x dependencies). >> >
