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
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
Looking at:
http://brutus.apache.org/gump/public/excalibur/excalibur-logger/gump_work/build_excalibur_excalibur-logger.html
I see Maven thinks these are unsatisfied:
The build cannot continue because of the following unsatisfied
dependencies:
avalon-framework-4.1.5.jar
-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
