One thing I've noticed is that as a rule of thumb, when something breaks in
GUMP, people tell the dependents to update. Hopefully, as GUMP pervades the
mindset for people, there will be equal pressure on dependencies to
stablize.
This is *not* to say that Log4J is doing anything wrong. I'm making a
purely generic comment that as GUMP becomes more widely used, it will force
everyone to be far more aware of the impact of their changes. It's great
benefit will be making reward vs cost equation clear early, providing better
opportunity for dependents and dependencies to discuss changes before things
are cast in stone.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
