Just because there hasn't been action doesn't mean it isn't important. I'm going to look over your patch and use it or extend it. Patch looked good, i.e., there were tests. The API isn't quite what I want ... I don't see the value of returning the injected service, simply invoking methods on the injected service should be sufficient.
On Tue, Jul 12, 2011 at 7:17 AM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > On Tue, 12 Jul 2011 11:11:33 -0300, Denis Stepanov > <[email protected]> wrote: > >> I understand :), it would be nice to have the easiest way to contribute, >> I can see how github is way ahead on it. > > The Tapestry contribution process is the Apache one and we can't really > change it unless the framework leaves Apache. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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]
