Re: Avalon artifactIds (was Re: Excalibur & Gump/Maven)
Adam, Just a stab, but it appears to be the latter. The projects using Avalon may need to switch to the new id's. I'm guessing that the projects in question are using an older version of avalon-framework that has since been refactored, hence the disjoint in dependencies? - Brett On Sat, 9 Oct 2004 07:07:15 -0600, Adam R. B. Jack <[EMAIL PROTECTED]> wrote: > > 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 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Avalon artifactIds (was Re: Excalibur & Gump/Maven)
> 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
RE: Avalon artifactIds (was Re: Excalibur & Gump/Maven)
> -Original Message- > From: Adam R. B. Jack [mailto:[EMAIL PROTECTED] > Sent: 08 October 2004 22:58 > To: Apache Gump > Subject: Avalon artifactIds (was Re: Excalibur & Gump/Maven) > > Ok, we are now down to this: > > > BTW: Anybody else to tell me what avalon-framework in Maven land is ins > Gump > > land? I think we have three dependencies, to it's one (a concern). Which > > ought I pick? "avalon-framework-api" or "avalon-framework-legacy" or > > "avalon-framework-impl"? Do we have a Gump/Maven disconnect here (due to > > changes in Avalon's artefacts) that needs to be updated in the Excalibur > > project.xml? 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. Stephen. > regards > > Adam > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
