Ehcache core and debugger supports 1.4, 1.5 and 1.6 at runtime. Ehcache final releases are compiled with -target 1.4. This produces Java class data, version 48.0. Ehcache server requires Java 1.5 or higher.
Because of an RMI bug , in JDKs before JDK1.5 ehcache is limited to one CacheManager operating in distributed mode per virtual machine. (The bug limits the number of RMI registries to one per virtual machine). Because this is the expected deployment configuration, however, ther should be no practical effect.
On JDK1.5 and higher it is possible to have multiple CacheManagers per VM each participating in the same or different clusters. Indeed the replication tests do this with 5 CacheManagers on the same VM all run from JUnit.
Not required from ehcache 1.6 on.
Ehcache core and debugger requires commons-logging commons-logging is a very common dependency, and is therefore not included in the distribution.
It is included in the tarball and the maven dependencies.
Not required from ehcache 1.6 on.
Ehcache core and debugger require Backport Concurrent. Rather than using the library which maven will pull down, users should consider using the version for their specific version of Java. This is not something that Maven can handle automatically. A JDK specific version should be faster than the generic one. See http://dcl.mathcs.emory.edu/util/backport-util-concurrent .
The management package of ehcache core requires JMX. Version 1.3 or higher will work. This is optional and only required if you are using the ManagementService .
Of course JDK1.5 has it built in.
JGroups has a "provided" scope in Maven and is not included in the tar ball.
If you wish to use the JGroups replication, add it manually.
Ehcache releases are placed in the central Maven repository.
The Maven snippet for ehcache 1.5.0, for example, is:
<dependency>
<groupId>net.sf.ehcache</groupId>
<artifactId>ehcache</artifactId>
<version>1.5.0</version>
</dependency>