The fact that it is part of tapestry /does/ count and /does/ make a difference. It means that we, the committers, have to fix it to work with any non-backwards-compatible changes that are made to internal classes /before/ a release can happen. Since the use of internal services is hidden by the module, users of the library are unaffected by these changes.
Counter that with external libraries, outside of tapestry. We don't control their release schedule, so a user depending on those libraries in their application, who wants to upgrade to the latest tapestry, is stuck. I'm not saying that making at least some of these services public is incorrect or a bad idea. But there is definitely a distinction between modules that are part of the tapestry project, and modules that aren't. Robert On Jul 20, 2010, at 7/203:12 AM , Piero Sartini wrote: >> Well that's definetely not a bug. Andreas talked right, he said >> "ideally", but tapestry-hibernate is a library around (very near) the >> core framework so if it choose to depend on an "internal" >> implementation it's a library's owner choice. What has not to be done >> is to public (in any way) the internal API on which the module/library >> depends on. >> This is the same choice ChenilleKit as done since day one. > > I think if tapestry-hibernate needs to use internal APIs or doing so > makes live much easier, we should think about making them public. We > should make module developer's live as easy as possible. > The fact that tapestry-hibernate is part of tapestry does not count in > my oppinion. Tapestry should be able to showcase its extensibility > within its modules. After all its a matter of eating our own dogfood. > > Piero > > --------------------------------------------------------------------- > 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
