A few people have noticed some significant changes in Tapestry 5.0.12-SNAPSHOT.
What's going on is a limited number of interface and package renames to support deploying Tapestry 3 or 4 and Tapestry 5 in the same web application (WAR). Most of the conflicts were related Tapestry annotations in T4 vs. T5. The org.apache.tapestry.annotations package was renamed to org.apache.tapestry.annotation (for T5) so as not to conflict with the same named package, and overalapping annotation class names, from T4. I'm still experimenting, but this "dual headed" deployment will be the best upgrade path from T3/T4 to T5. I expect to follow up with new T5 tools to make sharing data between the apps easier. Sorry for the disruption this late in the game. The question is: would it have been better to just broadly rename org.apache.tapestry to org.apache.tapestry5? There was quite a bit of discussion back on forth among the developers on this one. -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
