Mailing-List: contact dev-help@excalibur.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Excalibur Developers List" <dev@excalibur.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
From: Niclas Hedhman <niclas@hedhman.org>
To: dev@excalibur.apache.org
Subject: Re: The YAAFI Manifesto - WAS Re: Plans for Fulcrum release ....
Date: Fri, 18 Feb 2005 18:26:51 +0800
User-Agent: KMail/1.7.1
Cc: Turbine Developers List <turbine-dev@jakarta.apache.org>,
   server-dev@james.apache.org
References: <1108647297.6393.8.camel@zacarias>
 <7a31ebb305021715526cfc8bf0@mail.gmail.com> <4215BCE2.8050200@it20one.at>
In-Reply-To: <4215BCE2.8050200@it20one.at>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200502181826.51929.niclas@hedhman.org>

On Friday 18 February 2005 18:01, Siegfried Goeschl wrote:
> Hi Aron,
>
> I would like to point out that there is the James project suffering
> badly from the Avalonic wars (hence the cross-posting to the James
> Developer List). They recently had a long discussion to make an
> Avalon-free JamesNG
> (http://www.mail-archive.com/server-dev@james.apache.org/) but my gut
> feeling is that it won't be an easy task.

A previous discussion led to the conclusion that all configuration and 
deployment files must be interpreted as they are now, which leads to an 
immense compatibility issue, since you effectively need to be Phoenix/Loom 
compatible in every respect.

Now, perhaps such ambitions drop over time, but if not, then I think that 
either James resurrects Phoenix as their own internal container (much like 
Cocoon now have their own ECM+) or a migration to Loom are the only 
reasonable paths forward.

Cheers
Niclas

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