WTP is a bloated POS anyway. Completely agree that TapestryTools should not be dependent on it. I also can't use it because I keep my plugins up-to-date and not dare re-installing it as well.
On Feb 7, 2012, at 2:04 AM, Kalle Korhonen wrote: > 2012/2/6 Gavin Lei <gavingui2...@gmail.com>: >> After discussion with my GSoC mentor Igor Drobiazko, we think there >> are two ways for TapestryTools to go: >> 1. build TapestryTools on WTP, and keep improving it >> 2. build a brand new simple tool which supplies some special Tapestry5 >> features, and it can run without WTP > > +1 for simple and light. It wins every time. So far, haven't been able > to use your tool because I always keep my Eclipse up-to-date and I > wouldn't dare reinstalling all of it. > > Kalle > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
