Date: 2004-05-05T00:56:19
Editor: 203.121.47.163 <>
Wiki: Apache Avalon Wiki
Page: Reorganization
URL: http://wiki.apache.org/avalon/Reorganization
no comment
Change Log:
------------------------------------------------------------------------------
@@ -187,22 +187,25 @@
1. Hamilton Verissimo de Oliveira
1. +1 Carsten Ziegeler
- 1. Castle/Avalon''''''Net is an ''dotNet''/Csharp container implementation 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) should
be designed in such a way as to not have heavy side-effects. A heavy
side-effect would be to enforce one way of performing classloading, or to
enforce the use of a repository, etc.
+== Resolved Issues ==
== Resolved Issues ==
=== Avalon Logging ===
- 1. Avalon Logging (avalon/logging) has previously been touted as a
replacement of the older excalibur-logger, and is fairly flexible and powerful.
However, currently Avalon Logging depends on Repository (avalon/repository) for
Jar management and classloader establishment, and that dependency is possibly
not in the interest of the Fortress project, whereas the more generic 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 submit back to
Avalon a more generic solution.
+ Avalon Logging (avalon/logging) has previously been touted as a replacement
of the older excalibur-logger, and is fairly flexible and powerful. However,
currently Avalon Logging depends on Repository (avalon/repository) for Jar
management and classloader establishment, and that dependency is possibly not
in the interest of the Fortress project, whereas the more generic 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 submit back to
Avalon a more generic solution.
1. Fortress has to focus on limiting its dependency list rather than
expanding 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 mission.
Put shortly, the repository '''can''' be used if present, but should '''not be
required''' to be used.
'''''Resolution:''''' Avalon Logging is moved to the Merlin TLP, and the
Merlin group will invesigate the 'generalization' of the codebase.
+=== AvlonNet / Castle ===
+ Castle/Avalon''''''Net is an ''dotNet''/Csharp container implementation of
the AF4. There are several options.
+ 1. It stays for the time being in the Avalon Sandbox.
+ 1. It is moved to Incubation.
+
+'''''Resolution:''''' AvalonNet remains in the Avalon-Sandbox.
+
== Resolution Drafts ==
* [http://www.apache.org/~mcconnell/merlin/pub/docs/resolution.txt
MerlinTLPDraftResolution]
* [http://wiki.apache.org/avalon/Reorganization_2fDraftBoardResolutions
FortressTLPDraftResolution]
-
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
