On Mon, Oct 13, 2008 at 11:04 AM, Michiel Meeuwissen <[EMAIL PROTECTED]> wrote: > On Mon, Oct 13, 2008 at 10:20, Ernst Bunders <[EMAIL PROTECTED]> wrote: >> the tag files. So a bit of work there. Perhaps the tag files could be >> moved into the jar. > > That would be the most obvious solution. Several applications and > contributions already do that. Most noticeably, the mmbase-taglib > itself includes a few tagfiles. > > It is a sad thing that the URI of taglibrary then changes, so i find > my self maintaining two uri's in jsps I use for testing a tagfile > library (one pointing to WEB-INF/tags, one to the jar). Did not find a > solution for that yet.
yeah, I can imagine that it is not nice to use tagfiles in the jar, while you are developing on those tag files. For that reason mainly i wanted to keep them in the WEBINF/tags directory. So, would it be a problem to expand the mmbase-module format to include tag files (like i did with the ant applications build? I don't really see a problem with that. > > >> What's missing: documentation mostly, and tld's would be nice for >> editor support. As a side project I am working on a tool that can >> generate tld's from tag files. But that's not finished yet, and i >> don't know when this could be ready. It is a lot of tedious work to >> manually create those files, and then to maintain them. > > Why is that so tedious? It is actually very little work. You only have > to _mention_ the tag-file in the tld, and it works. What works then? I would like to have tld's that have information about all the properties and so on. What does a tld do that only mentions the tag files. Is that required for putting them in the jar? > I may assume that > you don't create a new tag-file so very often. Indeed tag-files > support a way to include also documention for itself and for its > attributes, and I have no idea how to convert that to actual > documentation, besided hand-crafting a tool. But surely something most > exist already, for that. That is exactly what my tool is doing. parse the files and create a model containing all relevant information. this model can than be dumped to xml, and transformed as you wish. I have been looking for a tool like this, but did not find it. I actually started building it as a programming exercise. But I think it can be quite useful. > >> >> So, let me know what you think. > > I would have no objections. To be included in the nightly (and > distribution) build, and hence the maven repository, it should build > with maven1.1, though. OK. So that leaves to decide if we expand the mmbase-module format to include tag files, or put the tag files in the jar. My preference goes to the first option. What do you think? regards, Ernst > > Michiel > > > -- > mihxil' http://meeuw.org > nl_NL eo_XX en_US > _______________________________________________ > Developers mailing list > Developers@lists.mmbase.org > http://lists.mmbase.org/mailman/listinfo/developers > > _______________________________________________ Developers mailing list Developers@lists.mmbase.org http://lists.mmbase.org/mailman/listinfo/developers
