Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Message-ID: <40694.160.33.98.118.1092662837.squirrel@160.33.98.118>
Date: Mon, 16 Aug 2004 09:27:17 -0400 (EDT)
Subject: RE: Patching Phoenix
From: "J Aaron Farr" <farra@apache.org>
To: server-dev@james.apache.org
Cc: dev@avalon.apache.org
Reply-To: farra@apache.org
User-Agent: SquirrelMail/1.4.3a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

-----Original Message-----
From: Hes Siemelink [mailto:hes-list@izecom.com]
Sent: Monday, August 16, 2004 9:10 AM
To: server-dev@james.apache.org
Subject: Patching Phoenix

> Hello
>
> I found the bug that caused James to cough when started in a directory
> path with spaces (like �C:\Program Files��).
>
> It�s a method in Phoenix that doesn�t properly encode URLs (see bug
> JAMES-307).
> I have a fix for JDK 1.4 (and I�m sure it won�t be difficult to produce
> something for 1.3 as well).
>
> The question is how to apply it� As I understand it, Phoenix development
> is frozen. Does this mean there won�t be any new releases? I thought of
> mailing the guy that wrote the Phoenix source, but it appears he�s not
> with Apache anymore.
>
> Any thoughts on how to deal with this?

The Phoenix code is still in Avalon's SVN:
  http://svn.apache.org/repos/asf/avalon/cvs-migration-snapshot/avalon-phoenix/

And any Avalon developer can still commit to it.  So it hasn't been
actually frozen, but there aren't many developers in Avalon at the moment
who work on it.  Peter Royal is still around and does quite a bit of work
on a fork of Phoenix called Loom which is alive and well in Codehaus.  I
would say, get his attention and he can probably apply the patch to both
Phoenix and Loom.  If that doesn't work, I'll apply the patch myself.

As for Peter Donald who authored a lot of Phoenix, he's now active in the
new Excalibur project which spun out of Avalon this last spring. 
(http://excalibur.apache.org)

If you have a collection of patches for Phoenix, I'm more than willing to
work with James in getting a new release out.  However, I imagine it would
only be a "maintenance release."  I doubt there are enough developers
right now willing and able to do any major work on it.  Instead, everyone
is more interested in newer container development like Loom or Merlin.

There was also discussion of setting up access to Phoenix for James
developers at one point or creating a "fork" for James.  I'm not sure what
the status of this is though.

jaaron

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