I'm interested in creating an alpha release soon. I'm just dealing with some of the remaining issues w.r.t. the build.
As an alpha release, I hope people would be ok with a few limitations: - Just Maven artifacts, no binary/source - No Maven quickstart archetype - No "site reports" beyond JavaDoc (I'll miss the code coverage report, though) These issues would be corrected in a later alpha or beta release. The point is to roll out something that many people can use, to start identifying problems in the rather large internal changes under the covers. I know I could keep adding new features forever, but it might be better to draw a line in the sand, get a 5.3 out in the next few months, and focus on a 5.4 for 2012. This might also be a good time to review what goes into the binary release. Currently, its the Tapestry jars and their dependencies, including the Antlr runtime, and Javassist (for the meantime) and some of the Hibernate and Spring modules. To be honest, I'm not sure if that's entirely legit (especially the Hibernate modules) and perhaps we should limit the JARs to tapestry-core & its dependencies, but the JARs for tapestry-hibernate and tapestry-spring w/o the Hibernate and Spring dependencies. -- 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]
