While testing the Magic javadoc plugin I was confronted with a issue that has been bothering me for a while. Avalon Framework API contains the deprecated Loggable interface. Loggable references the LogKit Logger interface. As LogKit has not api/impl separation, this means that strictly speaking, Avalon API has structural dependencies on LogKit, JMS, Sun's Mail API and JMS. Collectively this makes for one ugly api when generating with an automated source path ... i.e. the truth is exposed.
I have just resolved this issue by creating avalon-framework-legacy. I have moved the Logger interface and the entire component package from framework api into legacy, declared the legacy as dependent on the clean framework api, and updated the framework impl definition to reference both api and legacy.
I've committed these changes so people can so the overall impact, and I've bumped framework to 4.2.1. Initial test results under the javadoc plugin are now working nicely aside from some warnings which I'll take care of shortly.
Stephen.
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
