dev@woodstock.java.net

Re: How can I find out what source files were updated for issue 823

From: Ratnadeep Bhattacharjee <Ratnadeep.Bhattacharjee_at_Sun.COM>
Date: Thu, 06 Dec 2007 16:37:56 -0500

Bob Yennaco wrote:
> At one time we had such a tracking facility hooked into our internal CVS
> servers. But that facility is not hooked into the CVS server on
> java.net (at least none that I'm aware of). I agree it's a very
> necessary thing to have.
>
> Brett M. Bergquist wrote:
>> But 4.1.1 is not even available on the download site yet. This is not
>> a solution to my problem and I really need to fix just the Tree
>> rendering. Maybe even just a description of what newlines were
>> removed so that I can do the same here would work.
>>
>> I'd really like to know how one tracks a fix for an issue back to the
>> source code changes that were made. Surely there must be some
>> traceability. Here at my company we use CVSZilla which associates
>> checked in files with a bug in BugZilla. So from a bug in BugZilla, I
>> can find a CVS "transaction" that lists all of the source files that
>> were checked in to fix the bug.
>>

When we checkin code associated with a bug fix, the bug number is
usually part of the checkin. That probably doesn't help if you much if
you do not receive CVS notifications. This tree bug was unique in that
the fix was not in the tree but spread elsewhere in code that the tree
used. Hence, there wasn't any checkin specifically related to this bug.


>> Ratnadeep Bhattacharjee wrote:
>>> Brett M. Bergquist wrote:
>>>> This issue
>>>> https://woodstock.dev.java.net/issues/show_bug.cgi?id=823 is present
>>>> in the NB 6.0 release of the woodstock components. I cannot ship
>>>> with the tree acting the way that it is, so I need to apply the
>>>> fixes that were done to fix this issue to the 4.1 build 15 source
>>>> and rebuild myself. So how can I find out what files were updated
>>>> to fix this issue?
>>>>
>>>
>>> The fix was not in a single place but rather a number pf places where
>>> newlines were removed. I believe version 4.1.1 of Woodstock the issue
>>> has been resolved.
>>>
>>> -Deep.
>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_woodstock.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_woodstock.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_woodstock.dev.java.net
>>> For additional commands, e-mail: dev-help_at_woodstock.dev.java.net
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: dev-help_at_woodstock.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_woodstock.dev.java.net
> For additional commands, e-mail: dev-help_at_woodstock.dev.java.net
>