It's far from dead ... it's just that I went directly from 1.1-SNAPSHOT (5.2) to 1.2-SNAPSHOT (5,3).
Moving the Kaptcha component up would be ok ... could that be a sub-project that contributed to core, rather than directly in tapestry-core? As cool as "kaptcha" is, it's only one approach and I'd hate to give the impression that it was the only sanctioned approach. On Sun, Jul 24, 2011 at 5:40 AM, Igor Drobiazko <[email protected]> wrote: > T5.3 and tapx 1.1-SNAPSHOT are currently incompatible. Since some of the > features from tapx has been introduced in T5.3, there a some conflicts. It > looks like tapx is not under development for a long time now. > > The last remaining features, which I wish to be moved from tax into > tapestry, is kaptcha. This is a very useful component which should be part > of the tapestry distribution. There should be no problem with licensing as > kaptcha is distributed under Apache 2.0 license. > > http://code.google.com/p/kaptcha/ > > Any objections? If not, I would like to move the stuff. > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de > -- 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]
