Tapestry 5.4.5 is a drop-in replacement for Tapestry 5.4 releases. To upgrade, just update the dependency in your build configuration (Maven POM, Gradle build script, etc.) – or Download the new JAR file -- and the new version will just work. However, please review the How to Upgrade instructions before upgrading.
This is a recommended upgrade due to including security improvements.
Check 5.4.5 release notes for all the details.
We have created another release in the 5.4.x series. This should be a drop-in replacement for 5.4.x.
This is probably old news, but we have created another release in the 5.4.x series. Have a look at the release notes and give the latest version a spin while we pick up pace for Tapestry 5.5.
The long wait is finally over. We are happy to announce the availability of the 5.4.0 release.
Although a lot has changed under the hood, for most users, it should be a drop-in replacement for any version of the 5.3 series. Please head over to the Release Notes to read about the numerous changes that the 5.4.0 version brings and that make this release one of the best we ever made.
The release is available from the Maven Central Repository, or as a direct download.
And as always, if you experience any issues with the new version, please report them on the users' mailing list or create a JIRA issue.
Enjoy!
After a series of alpha and beta releases, some of which have been released into the wild, we're happy to announce that we created a release candidate for the 5.4 release.
We have fixed a couple of bugs, updated some internal libraries and improved performance and stability.
This release is available from the Maven Central Repository, or as a direct download.
Please give it a spin and let us know how it is working for you. If you find any bugs, please report them on the users' mailing list or create a JIRA issue.
Happy testing!
Tapestry 5.4-beta-26 fixes many bugs and paves the way towards the long awaited release candidate.
The release numbers are not consecutive because not every beta release is voted for wider release. This one has.
Tapestry 5.4-beta-26 contains a significant number of bug fixes and minor improvements. Dependencies on third party libraries have been updated.
We are making progress towards a release candidate.
- Fixed problems with tracking validation errors on fields inside Ajax updates
- Improvements to the exception report page, and the ability to write an exception report text file
- Fixed the layout issues related to the use of the Autocomplete mixin
- Converted the Autocomplete mixin to use Twitter Typeahead 0.10.5
- Fixed most compatibility issues with Internet Explorer 8
- Split more code out into smaller modules, to encourage reuse (even outside of a Tapestry web application)
- Fixed issues related to keyboard navigation and the modal dialog created by the Confirm mixin
- Removed the unused FormInjector component
Tapestry now requires at least JDK 1.6. It is no longer compatible with JDK 1.5.
While not an actual release candidate, beta previews like this one are high-quality builds that pass all of Tapestry's extensive automated tests and have been voted on by the Tapestry team.
Apache Tapestry 5.3.8: compatible with Java 8.
Tapestry is primarily available for download via Maven, from the Maven central repository:
<dependency> <groupId>org.apache.tapestry</groupId> <artifactId>tapestry-core</artifactId> <version>5.3.8</version> </dependency>
You can also download the binary, source, or JavaDoc archives.
Tapestry 5.3.8 is the latest maintenance release from the stable 5.3 release branch. If you intend to run this release on JRE 8, make sure to read the the release notes.
This release adds some stability fix for usage and hot deployment under Tomcat application server, a fix for JSR-303 for the BeanEditor component and a fix for the duplication of client ids generated by Tapestry5 on big pages (with a lot of components and concurrent accesses)
As usual for each Tapestry 5 release we've made great efforts to ensure an easy upgrade path; but be sure to read the upgrade notes carefully as some interfaces and methods that were deprecated in earlier major releases may have been removed: you should recompile and retest your application after upgrading your dependency. If you still have problems, use the Tapestry user mailing list to get support.
The release numbers are not consecutive because not every beta release is voted for wider release. This one has.
Tapestry 5.4-beta-22 contains a significant number of bug fixes and minor improvements. Dependencies on third party libraries have been updated.
- A "page loading mask" prevents interacting with the page until all JavaScript has downloaded and executed.
- It is now possible to unregister client-side DOM event listeners.
- The client persistence strategy now detects internal changes to mutable state objects.
- Page classes may now have the suffix "Page" (but this is not part of the page's canonical name, the one used in URLs).
- Selected pages may be loaded and initialized at server startup, rather than on the first request which references them.
- Tapestry does a better job of detecting when its naming rules would cause different pages, components, or mixins to share an alias.
- There were some issues with JDK 8 compatibility that have been addressed.
- Tapestry can now be configured to work in environments, such as Google App Engine, where file system access is prohibited.
- The exception report page and T5 Dashboard pages are no longer affected when the application overrides the Bootstrap CSS files in the core JavaScript stack.
- The Dashboard page now has a "Component Libraries" page that details information about all libraries in use by the application.
- It is possible to control whether a JavaScript library is minimized, or left as-is.
- The Import annotation on a base class would not operate correctly for a subclass; it now correctly searches relative to the base class.
- The PageActivationContext annotation now works for more than one field, allowing multi-part page activation contexts.
- Exception reports may now be written, in a plain-text format, to the file system.
Tapestry now requires at least JDK 1.6. It is no longer compatible with JDK 1.5.
While not an actual release candidate, beta previews like this one are high-quality builds that pass all of Tapestry's extensive automated tests and have been voted on by the Tapestry team.
The latest beta preview release of Tapestry 5.4 is now available.
The release numbers are not consecutive because not every beta release is voted for wider release. This one has.
<repository>
<id>apachestaging</id>
<name>Apache Staging Repository</name>
<url>https://repository.apache.org/content/groups/staging</url>
<layout>default</layout>
</repository>and here's the dependency:
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-core</artifactId>
<version>5.4-beta-3</version>
<type>jar</type>
</dependency>There is also a Maven archetype available, so you can build a quick little starter project as described at Getting Started, but specifying an alternative catalog:
-DarchetypeCatalog=https://repository.apache.org/content/groups/staging
A vote is underway for the 3rd beta preview release of Tapestry 5.4. This follows 2 other betas and 29 alphas for the work on version 5.4 that began over two years ago.
Apache Tapestry 5.3.7: improves security and stability.
Tapestry is primarily available for download via Maven, from the Maven central repository:
<dependency> <groupId>org.apache.tapestry</groupId> <artifactId>tapestry-core</artifactId> <version>5.3.7</version> </dependency>
You can also download the binary, source, or JavaDoc archives.
Tapestry 5.3.7 is the latest maintenance release from the stable 5.3 release branch. Full details are in the release notes.
This release adds some stability fix for usage and hot deployment under Tomcat application server, a fix for JSR-303 for the BeanEditor component and a fix for the duplication of client ids generated by Tapestry5 on big pages (with a lot of components and concurrent accesses)
As usual for each Tapestry 5 release we've made great efforts to ensure an easy upgrade path; but be sure to read the upgrade notes carefully as some interfaces and methods that were deprecated in earlier major releases may have been removed: you should recompile and retest your application after upgrading your dependency. If you still have problems, use the Tapestry user mailing list to get support.
A few days ago we changed our website infrastructure from a Confluence export that gets rsync'ed over several hosts until it reaches the ASF's main web servers to a SvnPubSub based approach. Now once an hour a buildbot build exports the site from Confluence and checks the changes into SVN where they get picked up by the public facing web servers almost instantly. This allows us to keep our old website sources in Confluence but also allows us to check in static resources like JavaDocs, XML schema files, DTDs, etc. directly into SVN and see the changes almost instantly. In addition, the new buildbot-run export cleans up almost every reference to Confluence, thus speeding up site rendering.
We also took the opportunity to clean up some of our legacy stuff. We took offline all documentation to the many previous versions of Tapestry and left only the static documentation (i.e. without the JavaDocs and reports) for Tapestry 3, Tapestry 4.1, and the latest version of Tapestry 5 online. If you require the documentation for another version of Tapestry, you will have to download the archived sources from http://archive.apache.org/dist/tapestry/ and build them for yourself. The JavaDocs and component reference for the current version of Tapestry 5 are linked from Documentation.
Apache Tapestry 5.3.6: improves security and stability.
Tapestry is primarily available for download via Maven, from the Maven central repository:
<dependency> <groupId>org.apache.tapestry</groupId> <artifactId>tapestry-core</artifactId> <version>5.3.6</version> </dependency>
You can also download the binary, source, or JavaDoc archives.
Tapestry 5.3.6 is the latest maintenance release from the stable 5.3 release branch. Full details are in the release notes.
This release adds hash-based message authentication to serialized object data stored on the client; this
improves security, and eliminates a potential denial-of-service attack. It also downgrades the included version of the Prototype JavaScript library back down to version 1.7 from 1.7.1; the newer version appears to have been causing compatibility issues with some versions of Internet Explorer.
As usual for each Tapestry 5 release we've made great efforts to ensure an easy upgrade path; but be sure to read the upgrade notes carefully as some interfaces and methods that were deprecated in earlier major releases may have been removed: you should recompile and retest your application after upgrading your dependency. If you still have problems, use the Tapestry user mailing list to get support.
The Tapestry Team is very proud to announce the availability of Apache Tapestry 5.3.5.
Tapestry is primarily available for download via Maven, from the Maven central repository:
<dependency> <groupId>org.apache.tapestry</groupId> <artifactId>tapestry-core</artifactId> <version>5.3.5</version> </dependency>
You can also download the binary, source, or JavaDoc archives.
Tapestry 5.3.5 is the latest maintenance release from the stable 5.3 release branch. Full details are in the release notes; This release fixes a number of minor annoyances, an important bug in how Tapestry manipulates Java bytecode, and includes fixes for several problems related to Internet Explorer compatibility (primarily, by upgrading Tapestry's built-in copy of Prototype to version 1.7.1).
Some testers have noticed an issue with Tapestry's DateField component not operating correctly in some versions of Internet Explorer. Please test carefully before upgrading.
As usual for each Tapestry 5 release we've made great efforts to ensure an easy upgrade path; but be sure to read the upgrade notes carefully as some interfaces and methods that were deprecated in earlier major releases may have been removed: you should recompile and retest your application after upgrading your dependency. If you still have problems, use the Tapestry user mailing list to get support.