Mailing-List: contact cvs-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: site-cvs@avalon.apache.org
To: site-cvs@avalon.apache.org
Subject: =?iso-8859-1?q?=5BApache_Avalon_Wiki=5D_Updated=3A__Reorganization?=
Date: Wed, 05 May 2004 07:54:10 -0000
Message-ID: <20040505075410.67940.83075@minotaur.apache.org>

   Date: 2004-05-05T00:54:10
   Editor: 203.121.47.163 <>
   Wiki: Apache Avalon Wiki
   Page: Reorganization
   URL: http://wiki.apache.org/avalon/Reorganization

   no comment

Change Log:

---------------------------------------------------------------------------=
---
@@ -190,17 +190,19 @@
  1. Castle/Avalon''''''Net is an ''dotNet''/Csharp container implementatio=
n of the AF4. There are several options.
   1. It stays for the time being in the Avalon Sandbox.
   1. It is moved to Incubation.
+ 1. Any core library (library housed and maintained in Avalon's core) shou=
ld be designed in such a way as to not have heavy side-effects.  A heavy si=
de-effect would be to enforce one way of performing classloading, or to enf=
orce the use of a repository, etc.
+
+=3D=3D Resolved Issues =3D=3D
+=3D=3D=3D Avalon Logging =3D=3D=3D
  1. Avalon Logging (avalon/logging) has previously been touted as a replac=
ement of the older excalibur-logger, and is fairly flexible and powerful. H=
owever, currently Avalon Logging depends on Repository (avalon/repository) =
for Jar management and classloader establishment, and that dependency is po=
ssibly not in the interest of the Fortress project, whereas the more generi=
c parts of Avalon Logging may be of greater interest. The Merlin committers=
 are suggesting that the Avalon Logging is initially moved to Merlin, where=
 the Merlin committers will try to remove the Repository dependency and sub=
mit back to Avalon a more generic solution.
   1. Fortress has to focus on limiting its dependency list rather than exp=
anding it.  A light footprint is important.
   1. Any reason why a simple Logger.getChildLogger() can't be done?
   1. Repository is a completely separate concern from logging, if "Avalon =
Logging" cannot be used without the repository, then it fails in its missio=
n.  Put shortly, the repository '''can''' be used if present, but should ''=
'not be required''' to be used.
- 1. Any core library (library housed and maintained in Avalon's core) shou=
ld be designed in such a way as to not have heavy side-effects.  A heavy si=
de-effect would be to enforce one way of performing classloading, or to enf=
orce the use of a repository, etc.
 =

-=3D=3D Resolved Issues =3D=3D
+'''''Resolution:'''''  Avalon Logging is moved to the Merlin TLP, and the =
Merlin group will invesigate the 'generalization' of the codebase.
 =

 =3D=3D Resolution Drafts =3D=3D
 =

  * [http://www.apache.org/~mcconnell/merlin/pub/docs/resolution.txt Merlin=
TLPDraftResolution]
  * [http://wiki.apache.org/avalon/Reorganization_2fDraftBoardResolutions F=
ortressTLPDraftResolution]
-
=20

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org