Stephen, >>>> This is possible without including any reference or depedency on >>>> Merlin providing we settle the.xinfo DTD. I would like at add >>>> another couple of points: >>>> >>>> 5) utilities enabling component migration >>>> >>>> One of the problems I have had to deal with concerning existing >>>> components are references to things like BlockContext. Merlin can >>>> work around this through its context management system. A >>>> container >>>> indepedent solution called GenericBlockContext was added to the >>>> Phoneix CVS. This seemed the correct thing to do as opposed to >>>> creating a Phoenix depedency in the Merlin CVS. >>>> >>>> The original contribution is under the Phoenix CVS (Attic). >>>> org/apache/avalon/phoenix/tools/export/GenericBlockContext. >>>> >>>> Are there any objections/issues to bringing this class back into >>>> action? >>> >>> >>> >>> >>> >>> As nobody has objected to this I'll go ahead an re-commit >>> GenericBlockContext. >> >> >> >> I for one would like more time to consider this. Please tread >> carefully dude given recent events. > > > > No problem. > I'll continue the work on Merlin in the meantime - more to be done on > documentation, demos, etc.
Could you give us a an overview of these changes and their expected usage, please Stephen? I'm having trouble seeing the immediate need..... - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
