CODETOOLS-7901466 is fixed but the bug is still open ?!?

Staffan Larsen staffan.larsen at oracle.com
Wed Aug 10 06:22:00 UTC 2016


> On 9 aug. 2016, at 17:45, Volker Simonis <volker.simonis at gmail.com> wrote:
> 
> On Tue, Aug 9, 2016 at 1:04 PM, Staffan Larsen
> <staffan.larsen at oracle.com <mailto:staffan.larsen at oracle.com>> wrote:
>> 
>>> On 9 aug. 2016, at 09:31, Volker Simonis <volker.simonis at gmail.com> wrote:
>>> 
>>> Hi,
>>> 
>>> CODETOOLS-7901466 has apparently been fixed in January:
>>> 
>>> http://hg.openjdk.java.net/code-tools/webrev/rev/09a9e40fb8ea
>>> 
>>> but the corresponding bug is still in status 'new':
>>> 
>>> https://bugs.openjdk.java.net/browse/CODETOOLS-7901466
>>> 
>>> How can this happen?
>> 
>> Unlike the JDK project, issues in CODETOOLS are not auto-closed when fixes are pushed to mercurial. Instead, they need to be manually closed.
>> 
> 
> Thanks, I didn't knew that.
> 
> Is it so hard to configure the repository such that it auto-closes the
> corresponding bugs on commit?

I don’t know how the mechanics for this work.

/Staffan

> 
>> /Staffan
>> 
>>> 
>>> Regards,
>>> Volker



More information about the code-tools-dev mailing list