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 2
> 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.
> -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 w
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
