It would be nice if the core implementations were included with Tapestry as a "default implementation" package, so they are easier to override. Like the way we used to drop in the contrib jars.
On 10/22/07, Fernando Padilla <[EMAIL PROTECTED]> wrote: > I will support this idea. > > specially if components are broken up too, base components, html > components, etc. > > Christian Gruber wrote: > > Hi, > > > > I realize that -annotations has already been converted, but I'm > > wondering if it wouldn't help reuse and modularity to take the raw APIs > > (key interfaces) and some other bits, including components and separate > > it from core. This came from looking at the redijedi stuff and how it's > > linked to 5.0.5. It seems to me that there's some raw API stuff that > > won't change between minor versions (now) and that 3rd party component > > libraries or other things would be able to depend on those without > > having to re-set or nudge versions numbers every time a bugfix release > > is made. > > > > Christian. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
