I think it is important to keep focused; Tapestry is targetted as a web framework, not a utilities collection. There's seperate libraries at Apache for that, and only the desire to be selective, and to minimize dependencies (and thus, potential dependency conflicts) has kept me from using those libraries. It's different for applications.
Every extra public class is that much more to maintain, field bug reports for, keep backwards compatibility on. Lastly, with luck, the RC boat has sailed ... 5.0.16 should (barring any currently unknown problems) be the RC and the final release. Use the internals, they won't burn you if you keep to the simple, stable stuff like Defense and CollectionFactory. On Tue, Nov 11, 2008 at 7:03 AM, Massimo Lusetti <[EMAIL PROTECTED]> wrote: > Hi devs, > does classes like Defense or ClasspathResource deserve the > internal.* package or maybe they could be elevated to be public > classes? > > I know the internal package name means they could break backward > compatibility without any warrant but the come to be useful > sometimes... expecially Defense. > > What do you think? > > Regards > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
