Return-Path: 
 <dev-return-32771-apmail-avalon-dev-archive=avalon.apache.org@avalon.apache.org>
Delivered-To: apmail-avalon-dev-archive@www.apache.org
Received: (qmail 36196 invoked from network); 12 Jul 2004 19:36:23 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 12 Jul 2004 19:36:23 -0000
Received: (qmail 1909 invoked by uid 500); 12 Jul 2004 19:36:22 -0000
Delivered-To: apmail-avalon-dev-archive@avalon.apache.org
Received: (qmail 1853 invoked by uid 500); 12 Jul 2004 19:36:21 -0000
Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@avalon.apache.org>
List-Subscribe: <mailto:dev-subscribe@avalon.apache.org>
List-Help: <mailto:dev-help@avalon.apache.org>
List-Post: <mailto:dev@avalon.apache.org>
List-Id: "Avalon Developers List" <dev.avalon.apache.org>
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Delivered-To: mailing list dev@avalon.apache.org
Received: (qmail 1835 invoked by uid 99); 12 Jul 2004 19:36:21 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [170.190.17.220] (HELO jismsg1.nashville.org) (170.190.17.220)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 12 Jul 2004 12:36:18 -0700
Received: by jismsg1.nashville.org with Internet Mail Service (5.5.2653.19)
	id <LP8FL5R3>; Mon, 12 Jul 2004 14:39:35 -0500
Message-ID: 
 <D78EC74BB0600241A3EE06FA8E0FEA9F06710C74@jismsg01.jis.nashville.org>
From: "Bennett, Timothy (JIS/Applications)"
	 <TimothyBennett@jis.nashville.org>
To: 'Avalon Developers List' <dev@avalon.apache.org>
Subject: RE: Avalon Versions
Date: Mon, 12 Jul 2004 14:36:31 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

> -----Original Message-----
> From: Niclas Hedhman [mailto:niclas@hedhman.org] 
> Sent: Monday, July 12, 2004 2:18 PM
> To: Avalon Developers List
> Subject: Re: Avalon Versions
> 
> Where is the technical problem between AF v4.1.5 and v4.2?
> 
> 1. No change in the AF code itself.
> 
> 2. A Specification Clarification that 4.2 components can 
> declare the Life cycle artifacts in their constructor, 
> instead of the phased population. Containers that does not 
> support this feature, will not be considered 4.2 compatible.
> 
> 3. All 4.1.x components will work in 4.1.x and 4.2 compliant 
> containers.
> 
> 4. Avalon is saying to its users; "Framework is NOT enough to 
> declare a compatible component contract. Containers SHOULD go 
> beyond Framework, and Avalon is providing the tools." You are 
> free to use or ignore this recommendation.
> 
> 5. The roadmap will be pointing to an Avalon 5, which will 
> REQUIRE containers to support a water tight component 
> contract, and not free to introduce incompatibilities in the 
> component-side contract, but free to add extensions 
> elsewhere. Hence the introduction of a "Facility" concept in 
> Merlin to make the distinction clear.
> 

Bingo.

I fail to see why AF4 is a *moving target* for the containers outside of
Apache-Avalon. It's not a moving target.

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