> avalon-framework-api > > this project defines the client API (interfaces, exceptions, > immutable datatypes, etc. dealing with component lifecycle concerns). > > avalon-framework-legacy > > contains some deprecated classes that have structural dependencies > on the avalon-logkit project. Is dependent on the framework api. > > avalon-framework-impl > > an implementation of the framework api. Is dependent on the > framework api and framework-legacy. > > As to what's needed by Excalibur Logging - you would need to ask someone > from the Excalibur project.
The problem we have is matching these to their Maven artifactIds. For Maven to be able to build things on top of Avalon (via Gump) we need Avalon's Gump descriptor <jar id="xxx" entry to match what Maven refers to these as in the project descriptor. Can Magic (or whatever creates descriptors) do this? Does having 3 jars here mean things in Maven land need to change, do they need to start using three artifact Ids? regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
