On 13-May-04, at 21:44 Uhr, robert burrell donkin wrote:
suitable for a general library but might be fine as a configuration for use with jelly.
Sorry to be picky but that was addressed solely for the purposes of Maven. The latter uses, I think, Jelly to parse such things as maven.xml and Digeser to parse project.xml.
Things should be looked at around maven thus.
A good candidate issue was the build of the jelly taglibs which should (but don't as it doesn't work) be importing a common entity for dependencies, this happening from inside a parent-project.
(e.g. from Jelly home, ./jelly-tags/swing/project.xml is declared child of ./jelly-tags/taglib-project.xml, itself should import (in an entity fashion) ./commonDeps.ent, this last import doesn't work).
paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
