> It is an unfortunate situation, but I think the path that will cause the > least pain now and in the future is to bite the bullet and do it. There > aren't too many mailets that use a ComponentManager / ServiceManager and > for those the code change is trivial.
Additionally it is *not* actually part of the API, that I can see. It is mailet developers accessing James in a way incompatible with the API. Therfore we IMO we *don't* owe them an warning. What we do owe them is a mailet API that allows mailets to access repositories without recourse to James or Avalon. The alternative is to consider moving James away from Avalon, either by maintaining our own fork, or by abandoning it completely, a move which has seen support from commiters in the past, but never been the subject of a vote. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
