Berin Loritsch wrote:
>
> ----- Original Message -----
> From: "Charles Benett" <[EMAIL PROTECTED]>
> To: "JAMES" <[EMAIL PROTECTED]>
> Sent: Friday, November 03, 2000 7:51 AM
> Subject: [Proposal] Upgrading to Avalon3.0a3
>
> > Unless anyone objects - or can think of a better approach - I will make
> > a new directory in cvs 'newavalon' which can hold its own bin, lib, src
> > and build.xml. That way we can port to Avalon3.0a3 over a few days
> > (hopefully not weeks!).
> > Code in newavalon should compile, but need not run until all the pieces
> > are ported.
> > Once we have a port we can transfer the revised code to the main bin,
> > lib, src directories. (Until the next release of Avalon)
> > Thoughts,
> > Charles
>
> Actually, I would make the changes to the current CVS of Avalon main source
> code. I relaxed the requirements on ConfigurationBuilder, and introduced the
> ComponentSelector pattern that was supposed to make it into the release.
>
> All further changes I am making are going toward the Avalon proposal directory
> tree, because I am working on a new Configuration system. That is the version
> that Cocoon is integrated with.
It would be tough to port to a moving version (ie Avalon in CVS). Can
you do a mini release with the ComponentSelector pattern? (like Avalon
3.0a4 ??)
Any ideas when the all-new Configuration system is likely ? Not that we
want to wait for it.
Charles
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
