> Perhaps it would be a nice idea to ship 1.7 with the taglib > in a seperate jar. This will make it easier to upgrade only > the taglib, or to remove it completely if you don't like it.
What is the problem this is supposed to solve? Also, is it realistic to assume that changes in the taglib don't require updates to the MMBase core? My first impression is this is just going to create more confusion about releases - what versions of mmbase.jar and taglib are compatible - while directing attention away from regular maintenance and milestone releases. Rob van Maris Technical Consultant Quantiq xmedia & communication solutions
