Thiago, the main use case (and probably the only one for a quite long time) for plastic is Tapestry. Having plastic as a tapestry module has an big advantage when coding and improving Tapestry's features. I believe we should concentrate on this in the first place.
A lot of people are using tapestry-ioc without tapestry-core. Same will apply for plastic. On Mon, Mar 28, 2011 at 9:18 PM, Thiago H. de Paula Figueiredo < [email protected]> wrote: > On Mon, 28 Mar 2011 15:58:23 -0300, Davor Hrg <[email protected]> wrote: > > .. integrate into tapestry as it will be the main use for some time surely >> :) >> > > If Plastic's code is put inside Tapestry(-core or -ioc), nobody will use it > outside of Tapestry(-core or -ioc). The more people using it, the better. I > don't think there's a good reason to de-standalone something that is > standalone now. If there's no Apache guideline against linking to non-ASF > code, I'd suggest to keep Plastic in its current GitHub home. > > -- > 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] > > -- Best regards, Igor Drobiazko http://tapestry5.de
