Danny,

I submitted several patches.  More to come.  (I just read about the [PATCH]
prefix ... do I need to resubmit?)

It just would have been nice if whomever removed mysql from the SAR would
have posted a note so that I wouldn't have wasted an hour trying to figure
out why the package wasn't found, when it is plainly in the source lib/
directory.  Similarly, a quick note about PHOENIX_SECURE=false would have
been a help.

Anyhow, I'm not sure what to do about:

 1. PHOENIX_SECURE - hopefully Paul can clue us in, and I'm curious why no
one else ran into it.
 2. config.xml moved to SAR-INF - I wouldn't presume to update docs without
knowing if this is the intended new home.
 3. mysql - if this is permanently removed, then I'd be happy to update the
docs.  Otherwise, I'll submit a patch for build.xml.  Where did you leave
things off with him from the most recent discussion?

At least I took the time to make a note of things on the mailing list, so
that the next developer who runs into them can at least find info on the
issue.

        --- Noel

-----Original Message-----
From: Danny Angus [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 07, 2002 2:47
To: James Developers List
Subject: RE: mySQL caveat


Noel,
Mate.. we all know that there's a lot to do, patch things, patch the todo
list, use bugzilla.
d.

> -----Original Message-----
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]]
> Sent: 07 June 2002 06:28
> To: James-Dev Mailing List
> Subject: mySQL caveat
>
>
> Someone might have mentioned that the mysql driver was removed
> from the SAR.
> This leads to another thing that we'll need to document for
> installation and
> migration.
>
>       --- Noel
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to