... and the latest version of Tapestry, 5.2.2, is now available. This is the second beta release for Tapestry 5.2, addressing a few bugs in 5.2.1, and adding a couple of minor non-disruptive improvements ... read about it in the release notes.
Tapestry 5.2.2 is available for download, or via Maven:
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-core</artifactId>
<version>5.2.2</version>
</dependency>
I expect some minor issues will be addressed in Tapestry 5.2.3. Expect that in a week or so.
Just read the release note comment about the change in the Link's methods - and am asking my self how this relates to your "swarn" commitment to backword compatibility?
ReplyDeleteBackword compatibility is often a draw back, beacuase one is comitted to keep the public api as is, may be deprecate over time, but changing the contract is actualy a no go.
So why actualy not interoduce a new method with the new contract and keep the old one as is?
Would that cost so much? How much this cost weigh against braking compatibility?
To Ron:
ReplyDeleteI believe we should be more flexible. This change is "cheap" to follow (just a search&replace) and you would touch the project anyway when you replace the jars.
Adding new methods with similar name and function just makes it harder to understand the goal behind them.