3
* {Building an ehcache distribution from source}
5
To build Ehcache from source:
7
[[1]] Check the source out from the subversion repository.
9
[[1]] Ensure you have a valid JAVA_HOME and ANT_HOME configured with binaries for both in your PATH
11
[[1]] From within the ehcache/core directory, type <<<ant>>>
14
* {Running Tests for Ehcache}
16
To run the test suite for Ehcache:
18
[[1]] Check the source out from the subversion repository.
20
[[1]] Ensure you have a valid JAVA_HOME and ANT_HOME configured with binaries for both in your PATH
22
[[1]] The integration tests rely on a standard Tomcat to be installed. Define TOMCAT_HOME to point to a Tomcat 5 or 6 installation.
24
[[1]] From within the ehcache/core directory, type <<<mvn test>>>
26
[[1]] If some {performance tests fail}, add a <<<-D net.sf.ehcache.speedAdjustmentFactor=x>>> System property to
27
your command line, where x is how many times your machine is slower than the reference machine. Try setting
30
* Deploying Maven Artifacts
32
Ehcache has a repository and snapshot repository at oss.sonatype.org.
34
The repository is synced with the Maven Central Repository.
43
This will fail because SourceForge has disabled ssh exec. You need to create missing directories manually using
44
sftp access <<<sftp gregluck,ehcache@web.sourceforge.net>>>
48
(These instructions are for project maintainers)
50
You need the following unix utilities installed:
64
You also need a yDoc license.
66
With all that, build the site as below:
72
Unfortunately, sourceforge scp is broken, since they removed the ability for ssh to execute shell commands.
74
The site needs to be deployed from the target/site directory using:
76
rsync -v -r * gregluck,ehcache@web.sourceforge.net:/home/groups/e/eh/ehcache/htdocs
86
** {Sourceforge Release}
92
then manually upload to SourceForge
94
<<<sftp gregluck@frs.sourceforge.net>>>
96
and complete the file release process