I think there's a problem with the version number generation in the tapestry-core jar file ... you have to do a clean jar to get the file to update, otherwise an out-of-date version is included. I'll look into a fix when I get a chance.
Gradle is smart about these things; we can generate a new file on each jar build and Gradle will be smart enough to only rebuild the JAR if there's an actual change to the file (or some other resource packaged into the JAR). It's not based on timestamps ... Gradle keeps a hash of the file content for this purpose (it's really intended to deal with long toolchains related to source generated from SOAP files and the like). -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
