Tapestry can be downloaded in either binary or source format.
See the Release Notes for differences between versions and how to upgrade.
Stable releases should be relatively free of critical bugs and are considered the safest option if stability is a requirement.
Tapestry 5.3.7 was released on 24 Apr 2013. See the release notes for more details.
Note that the recommended distribution method of binary and source JARs is via Maven repository. Binaries, source code, and Javadocs are also available as a zip archive.
Tapestry 5.2.6 was released 29 Jun 2011 and is expected to be the final release of the 5.2 branch. See the release notes for more details.
Tapestry 4.1.6 was released on 07 Sep 2008 and is the final release of Tapestry 4. See the release notes for details.
Looking for an older version of Tapestry? Try the archives.
Releases Under Development
Releases under development are less stable; alpha releases are often incomplete; beta releases occur in the lead up to creation of a stable release.
Tapestry 5.4 is under active development. There have been more than twenty alpha releases so far. See the subdirectories of https://repository.apache.org/content/groups/staging/org/apache/tapestry/.
Nightly snapshot binaries are also available in Apache's Nexus Maven repository under the subdirectories of https://repository.apache.org/content/repositories/snapshots/org/apache/tapestry. Please be aware that nightly snapshots have not been reviewed and may have significant stability problems from time to time.
The source download links are listed in the boxes above. In addition, the source code can be checked out anonymously from Git with the clone command:
(See Building Tapestry from Source for more info.)
Versions 5.3.2 and earlier are also available via Subversion, at https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk/
Access from behind a firewall
Refer to the documentation of your Git client for more information about access behind a firewall. Generally this requires configuring access through a proxy (by specifying the proxy host and port) or opening up a port on the firewall.