Hi! > I was referring to the problems the user have with old libs in their > directories - with a clear package name in the game, we could more > easily find out where the problems are. But I can wait until after the > release, sure. > On the other hand we have to decide which burden we can put on our users. If every upgrade requires some drastic changes in the local setup this is a huge burden.
A user might also be a developer and as a developer one might create its own components - maybe reusing tomahawk stuff. Or those who created custom renderer classes for tomahawk components (like I've done) For the future we should find a way how to deal with such changes. In apache-commons you never ever can make such a drastic change between minor releases. So this change would require a tomahawk-2.0 release. Ciao, Mario
