> Okay, I'm getting ready to commit parts of the taglib to the repository...
> src/taglib is okay for that, right ?
Yes.
> Regarding the upcoming release, my priority is getting the taglib working
for
> the admin-webapp. That means that the taglib is mostly targeted at the
> requirements of the admin-webapp, and it is very likely that the taglib
itself
> will still (r)evolve quite a bit (before and probably even after 1.0
final). I
> believe we can declare the taglib "API" to be in an early stage, but still
> include it with the release while making sure it is in sync with the admin
> webapp.
Yes, that's reasonable, and we'll mention it in the release notes. I think
we should plan to stabilize that new API when we start freezing for the next
release.
Remy