---- Mario Ivankovits <[EMAIL PROTECTED]> schrieb: > I don't see any reason why we shoulnd't being able to provide a stable > api even for shared.
I have to strongly disagree here. The fact that a classpath can contain three different libs that depend on three different versions of shared is *really* important. Without this, every product that depends on shared would all have to be released at the same time, because myfaces-core-with-sharedx.y would be incompatible with trinidad-with-shared-x.z. And users would likewise have to upgrade simultaneously. This is not just a matter of keeping the api stable, but also the implementations. A change in behaviour in the implementation of a shared class could break some other lib when it is deployed. We see exactly these sorts of cascading issues with shared libs in places like a Linux distro for example. But a linux distro goes through first an "unstable" phase where all sorts of things *do unexpectedly* break due to sharedlib changes, then an extended beta/stabilisation phase where tens of thousands of users test it and report the problems. I don't think we can emulate that kind of cycle. Instead, with the current system we only need to test one product at a time, because each one has its own version of shared. For that kind of convenience, I'm willing to live with a little breakpoint awkwardness. Regards, Simon
