Velocity Engine




Translations (outdated)

Velocity News Feed

Velocity Dependencies

When building from sources, Maven should fetch all needed dependencies. At runtime, velocity only needs slf4j-api, and one of the slf4j bindings (needed classes from commons-lang and commons-collections are incorporated using "shading").

The following table lists all needed jars Velocity has a number of external jar dependencies. However, not all of these are needed every time. This document should help you do decide which jars must also be present if you want to integrate Velocity into your application.

All of these jars must be present when building Apache Velocity. The build process downloads all of them automatically from the Internet.

Jar name Version Compilation Tests Runtime Comment
slf4j-api 1.7.12 Yes Yes Yes you'll also need an slf4j binding at runtime
commons-collections 3.2.2 Yes No No Dependancy upon commons-collections-3.x is needed only by some deprecated classes and methods, so as to maintain backward compatibility, and will be dropped in a future version.
commons-lang 3.4 Yes No No
junit 3.8.1 No Yes No
hsqldb 1.7.1 No Yes No
commons-io 2.4 No Yes No
slf4j-simple 1.7.12 No Yes No Your application will need one SLF4J binding, see below
servlet-api 2.5 No No No Only needed in the context of a web application. Should normally be supplied by the servlet container.

At runtime, Velocity will require an SLF4J binding to be present in the path. Typically, one of: