Is there any technical reason to switch from the Avalon Logger
abstraction?
No.
Well ...then that's no good reason to me.
Rather I would also import the few classes
into out repository (like we did with ECM)
than doing the switch.
We can't import the classes in this case as these are interfaces. For
> ECM we could provide our own implementation, but - for now - we are
> still using the interfaces of the avalon framework.
...well interfaces then - whatever.
We agreed to move
away someday from these interfaces - and part of this logging discussion
is exactly about this: moving away from the avalon interfaces.
They would no longer be the "avalon interfaces"
..or is the ECM++ still avalon?
What was the reason again to move exchange the
abstraction layer? ...not talking about the
implementation.
Sorry, guys this discussion getting a bit absurd to me.
--
Torsten
