Playing devils advocate here for a bit .. --------- Sounds like a lot of work for a feature that many people would like but are not willing to put the time in for it.
Also, such a repository is a blessing and a curse - on many of the "plugin repositories" that I've seen (e.g. jquery, grails, netbeans), after a while it becomes a dumping ground for unmaintained plugins that reflects negatively on the parent project -e.g. if I get a crummy plugin from tapestry.apache.org/plugins, I'll be bitching on this list that the plugin sucks and is not maintained (which the core Tap devs have nothing to do with). Given the current reluctance (understandable) of the core T5 team to add even existing and well used components under the Tapestry umbrella, I don't see this happening. -------------- Cheers, Alex K On Mon, Apr 18, 2011 at 9:22 AM, antalk <ant...@intercommit.nl> wrote: > Something like this is what i'm looking for ! And i guess a lot of people > here also. > > This would be an excellent idea to integrate into the existing site. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/New-component-library-tp4310339p4310720.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > 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
