avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farr, Aaron" <Aaron.F...@am.sony.com>
Subject RE: [avalon] roadmap - library criteria
Date Wed, 03 Mar 2004 22:37:41 GMT

> -----Original Message-----
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> Sent: Wednesday, March 03, 2004 5:30 PM
> To: 'Avalon Developers List'
> Subject: RE: [avalon] roadmap - library criteria
> Aaron Farr wrote:
> >
> > Also, I would like to look into the Cocoon base again (it's
> > been a _long_
> > time) and see exactly where and how you're using
> > ECM/Fortress.  Is Fortress being used in the latest release(s)?
> >
> No :) The latest release is in the 2.1.x branch (2.1.4) and still
> uses ECM - which is for us absolutely perfect by the way. The only
> annoying thing is that we have one big configuration file for
> all components.

Not sure if moving to Fortress or Merlin would really help with that.

> The new version 2.2 which development has started some months ago
> and which will take some more months to get finished starts using
> Fortress. But it's not fully migrated yet due to the configuration
> problems I mentioned. If we move completly to Fortress we are
> not compatible to 2.1.x. If we are compatible, we could stay with
> ECM anyway :) (A little bit simplified but more or less this is
> the current problem).

Yeah.  I see the problem.  Preserving configuration file format would be
important from a user perspective.  I imagine most Cocoon users don't really
care about ECM/Fortress/Merlin, but if we tell them their configuration
files need rewritten...  :-)

Anyway, I'll try to find some time to look through the code.  It would help
me understand how the changes we're discussing could affect some of our

J. Aaron Farr
  (724) 696-7653

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

View raw message