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.
I'm ok with this change.
This would be easy to do, simply by moving the entire
org.mmbase.bridge.jsp.taglib tree to the 'applications' CVS module.
The package structure could possibly also be changed (perhaps org.mmbase.taglib or org.mmbase.bridge.taglib or org.mmbase.applications.taglib or so), but that is an other issue which I wouldn't dare to decide on yet.
I think this is very imported, just as Daniel stated, we have to agree on the naming issues. Is every extension on MMBase an MMBase-application? How do we name the applications build upon MMBase? Do we need a distinction between these sorts of applications? Etc. Just a few questions, but very important ones.
Gerard
Gerard
