Find attached to the Jira autologically named file
ESmeJira259PatchByRevertingTo_r942677_Reopens231Presumably.diff :-)
Somebody now needs to re-look at 231 :(
Imtiaz
----- Original Message -----
From: "Richard Hirsch" <[email protected]>
To: <[email protected]>
Sent: Sunday, August 22, 2010 12:35 PM
Subject: Re: Stax deployment with new code - despite bugs
The last stax deplyoment (
http://esmecloudserverapache.DickHirsch.staxapps.net) was on Jul 12,
2010.
D.
On Sun, Aug 22, 2010 at 8:54 AM, Imtiaz Ahmed H E <[email protected]>
wrote:
In that case, it will help to locate the problem if you can tell me the
date
of that deployment so that I can check the subsequent check-ins to see
what
happened.
I myself will not be looking at the Stax deployment.
Imtiaz
----- Original Message ----- From: "Richard Hirsch"
<[email protected]>
To: <[email protected]>
Sent: Sunday, August 22, 2010 12:13 PM
Subject: Re: Stax deployment with new code - despite bugs
If you take a look at the current deployment on stax, you will see
that it works there.
D.
On Sun, Aug 22, 2010 at 7:02 AM, Imtiaz Ahmed H E <[email protected]>
wrote:
Dick,
Following your earlier mail saying you find new bugs on your return,
this
morning I started investigating ESME-259 and it doesn't look like it was
working at any time. Not too sure. Still figuring it out. Will have it
done
asap.
Imtiaz
----- Original Message ----- From: "Richard Hirsch"
<[email protected]>
To: <[email protected]>
Sent: Sunday, August 22, 2010 10:04 AM
Subject: Stax deployment with new code - despite bugs
As I work towards the next release, I've found a new bugs in the
current source that don't exist on stax (For example,
https://issues.apache.org/jira/browse/ESME-259). I'd still like to
deploy it on stax.
Does anyone have a problem with that?
D.
