+1 for putting it on github. I don't think we should have two different APIs for the same thing. We have a new URL rewriting api now and the old one is deprecated. If somebody needs to use the "old" stuff, just create a new project on github.
On Sat, May 12, 2012 at 7:29 AM, Kalle Korhonen <kalle.o.korho...@gmail.com>wrote: > On Fri, May 11, 2012 at 10:46 AM, Thiago H. de Paula Figueiredo > <thiag...@gmail.com> wrote: > > On Fri, 11 May 2012 13:06:33 -0300, Denis Stepanov > > <denis.stepa...@gmail.com> wrote: > > I ended up figuring out what Denis described above and then I managed to > get > > everything set up now. By the way, is anyone against me creating a > separate > > subproject to provide the old URL rewriter API? I need it for a project > of > > mine and, from some recent messages in the mailing list, it seems more > > suitable for some scenarios that the LinkTransformer API. I'm also > thinking > > A separate sub-project as part of Tapestry? That sounds weird in a lot > of ways - so far, we haven't had any separately releasable modules and > we don't have any examples of competing implementations from different > committers. Why not just put it on github? > > Kalle > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > -- Best regards, Igor Drobiazko http://tapestry5.de http://twitter.com/drobiazko
