> Just to summarize: I'm +1 to add a new setter tag and make it > available for plugins. I may even be able to add it sometime > tomorrow if others Maven committers also agree. > > I think we have 2 solutions: > > 1/ We deprecate pluginVar, and create a new tag called > something like: getPluginVar. We add another new setPluginVar tag > > 2/ We add an "action" attribute to the existing pluginVar > tag, with 2 valid actions: "set" | "get". "get" being the default.
I prefer 2 for greater compatibility, but a different format. If "var" is present, it behaves as get, if "value" is present, it behaves as set, if both, it throws a JellyTagException. I'll post about the jelly tag lib separately. - Brett
