This is done using TUSCANY-2690. On Tue, Nov 25, 2008 at 9:33 PM, Simon Laws <[EMAIL PROTECTED]>wrote:
> > > On Tue, Nov 25, 2008 at 3:51 PM, Ramkumar R <[EMAIL PROTECTED]> wrote: > >> Hi Simon, >> >> Yeah right, I just noticed the conversation which happened sometime ago on >> this and there >> seems to be no concern in removing the monitor-logging module. >> >> *http://www.mail-archive.com/[email protected]/msg02282.html* >> >> Based on the above conversation and with no concern on this current >> thread, I will raise >> a JIRA to remove this module. >> >> >> On Tue, Nov 25, 2008 at 2:40 AM, Simon Laws <[EMAIL PROTECTED]>wrote: >> >>> >>> >>> On Mon, Nov 24, 2008 at 6:10 PM, Ramkumar R <[EMAIL PROTECTED]>wrote: >>> >>>> Hi All, >>>> >>>> The modules/monitor-logging provides pretty much the same functionality >>>> as the default modules/monitor. >>>> So it appears as a redundant module here. >>>> >>>> The only dependent on modules/monitor-logging is the itest/validation >>>> module. >>>> >>>> Basically I tried removing the monitor-logging from my local and did a >>>> bit of recoding in itest/validation >>>> module to use the default monitor and every things seems to be working >>>> fine. >>>> >>>> So my suggestion would be to remove the modules/monitor-logging from the >>>> trunk. +1 from me. >>>> >>>> Please let me know if any one have any concerns/comments on the same. >>>> Thanks. >>>> >>>> -- >>>> Thanks & Regards, >>>> Ramkumar Ramalingam >>>> >>> >>> Hi Ram >>> >>> Sounds good to me, we discussed this a while ago but I didn't get round >>> to it. >>> >>> Simon >>> >> >> >> >> -- >> Thanks & Regards, >> Ramkumar Ramalingam >> > > Great, thanks Ram. > > Simon > -- Thanks & Regards, Ramkumar Ramalingam
