commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject Commons/Avalon [was Re: [Logging] [VOTE] Commons Logging 1.0 Release]
Date Tue, 29 Jan 2002 22:11:21 GMT
If this keeps up I'm going to have to request a FAQ on what the deal with
Commons and Avalon is...

Is there a fundamental clash of philosophies between the two that is yet
to be resolved? Is it resolvable?

My understanding so far is that Avalon is a standard framework for
server-side applications, providing a set of common components to assist
in that framework.

And that Commons is a set of common components for use in any framework.

Avalon predates Commons, but has a less bazaar like atmosphere(?).

Given that the two projects share some part of their mandates at the
moment, should they integrate their internal communication somewhat to
ease things?

For example, when a new Avalon component or a new Commons component is
added, is there any form of cross-notification?

Who is the Avalon representative on the Commons project, and who is the
Commons representative on the Avalon project...

Just ideas...


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message