Leo Simons wrote:
Stephen McConnell wrote:
Perhaps I missed the conversation somewhere, but is there a plan to
establish a single set of tags that can be used with all three containers?
We have established a LCD set (which is a start but only really useful for Fortress). In principal the Merlin/Phoenix set could be converged reasonably easily as part of an expanded standard set that maintains consistency with the AMTAGS set.
can merlin parse the AMTAGS yet?
No.
:-)
How much work would it be to support it?
Not a lot!
Does it require modification of anything but merlin ant task?
That it - the classes for this are completely isolated.
I think it's sensible to first get the LCD to actually be LCD before starting on growing it :D
Here is a better proposal - lets outline the expanded set of tags and get concensus on the suite. What we have in Merlin at the moment is a constent set of tags and incorporating the LCD subset would make things inconsitent. I figure the better approach is to lay out the suite - migrate Merlin to the AMTAGS model and deal with the much more important point of establishing well defined requirements on containers to deal with "unsupported" or "unrecognized" tags in a well defined and consitent manner.
your royal pain in the ****,
Yep!
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
