From volker.simonis at gmail.com Tue Aug 9 07:31:06 2016 From: volker.simonis at gmail.com (Volker Simonis) Date: Tue, 9 Aug 2016 09:31:06 +0200 Subject: CODETOOLS-7901466 is fixed but the bug is still open ?!? Message-ID: 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? Regards, Volker From staffan.larsen at oracle.com Tue Aug 9 11:04:39 2016 From: staffan.larsen at oracle.com (Staffan Larsen) Date: Tue, 9 Aug 2016 13:04:39 +0200 Subject: CODETOOLS-7901466 is fixed but the bug is still open ?!? In-Reply-To: References: Message-ID: > On 9 aug. 2016, at 09:31, Volker Simonis 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. /Staffan > > Regards, > Volker From jonathan.gibbons at oracle.com Tue Aug 9 14:50:22 2016 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Tue, 09 Aug 2016 07:50:22 -0700 Subject: CODETOOLS-7901466 is fixed but the bug is still open ?!? In-Reply-To: References: Message-ID: <57A9EDAE.5070802@oracle.com> On 08/09/2016 12:31 AM, Volker Simonis 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? > > Regards, > Volker Volker, Thanks for the report. I will clean this up. -- Jon From volker.simonis at gmail.com Tue Aug 9 15:45:09 2016 From: volker.simonis at gmail.com (Volker Simonis) Date: Tue, 9 Aug 2016 17:45:09 +0200 Subject: CODETOOLS-7901466 is fixed but the bug is still open ?!? In-Reply-To: References: Message-ID: On Tue, Aug 9, 2016 at 1:04 PM, Staffan Larsen wrote: > >> On 9 aug. 2016, at 09:31, Volker Simonis 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? > /Staffan > >> >> Regards, >> Volker > From staffan.larsen at oracle.com Wed Aug 10 06:22:00 2016 From: staffan.larsen at oracle.com (Staffan Larsen) Date: Wed, 10 Aug 2016 08:22:00 +0200 Subject: CODETOOLS-7901466 is fixed but the bug is still open ?!? In-Reply-To: References: Message-ID: <42A4A273-BB65-45F1-A900-15819AA149EB@oracle.com> > On 9 aug. 2016, at 17:45, Volker Simonis wrote: > > On Tue, Aug 9, 2016 at 1:04 PM, Staffan Larsen > > wrote: >> >>> On 9 aug. 2016, at 09:31, Volker Simonis 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 From volker.simonis at gmail.com Wed Aug 10 07:39:22 2016 From: volker.simonis at gmail.com (Volker Simonis) Date: Wed, 10 Aug 2016 09:39:22 +0200 Subject: CODETOOLS-7901466 is fixed but the bug is still open ?!? In-Reply-To: <42A4A273-BB65-45F1-A900-15819AA149EB@oracle.com> References: <42A4A273-BB65-45F1-A900-15819AA149EB@oracle.com> Message-ID: On Wed, Aug 10, 2016 at 8:22 AM, Staffan Larsen wrote: > > On 9 aug. 2016, at 17:45, Volker Simonis wrote: > > On Tue, Aug 9, 2016 at 1:04 PM, Staffan Larsen > wrote: > > > On 9 aug. 2016, at 09:31, Volker Simonis 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. > CC'ed Iris who handles such questions for our porting repositories. @Iris: do you know how auto-closing bugs on submit can be configured for a repository? Apparently, the CODETOOLS repository doesn't have this feature. I think, aside from the technical realization, this feature has to be requested by the corresponding project lead, so I've also CC'ed Jonathan. Regards, Volker > /Staffan > > > /Staffan > > > Regards, > Volker > > From iris.clark at oracle.com Wed Aug 10 17:06:03 2016 From: iris.clark at oracle.com (Iris Clark) Date: Wed, 10 Aug 2016 10:06:03 -0700 (PDT) Subject: CODETOOLS-7901466 is fixed but the bug is still open ?!? In-Reply-To: References: <42A4A273-BB65-45F1-A900-15819AA149EB@oracle.com> Message-ID: Hi, Volker. > @Iris: do you know how auto-closing bugs on submit can be configured > for a repository? > > Apparently, the CODETOOLS repository doesn't have this feature. That feature is not available for the hg.ojn:code-tools/* forests because their bugs are not part of the JIRA "JDK" project (i.e. their bugs do not begin with "JDK-".) All tools/servers which trigger a bug update based on Hg push can only access the "JDK" project. It would be a non-trivial task to provide such support. Thanks, iris -----Original Message----- From: Volker Simonis [mailto:volker.simonis at gmail.com] Sent: Wednesday, August 10, 2016 12:39 AM To: Staffan Larsen Cc: code-tools-dev; Iris Clark; Jonathan Gibbons Subject: Re: CODETOOLS-7901466 is fixed but the bug is still open ?!? On Wed, Aug 10, 2016 at 8:22 AM, Staffan Larsen wrote: > > On 9 aug. 2016, at 17:45, Volker Simonis wrote: > > On Tue, Aug 9, 2016 at 1:04 PM, Staffan Larsen > wrote: > > > On 9 aug. 2016, at 09:31, Volker Simonis 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. > CC'ed Iris who handles such questions for our porting repositories. @Iris: do you know how auto-closing bugs on submit can be configured for a repository? Apparently, the CODETOOLS repository doesn't have this feature. I think, aside from the technical realization, this feature has to be requested by the corresponding project lead, so I've also CC'ed Jonathan. Regards, Volker > /Staffan > > > /Staffan > > > Regards, > Volker > > From volker.simonis at gmail.com Wed Aug 10 17:36:16 2016 From: volker.simonis at gmail.com (Volker Simonis) Date: Wed, 10 Aug 2016 19:36:16 +0200 Subject: CODETOOLS-7901466 is fixed but the bug is still open ?!? In-Reply-To: References: <42A4A273-BB65-45F1-A900-15819AA149EB@oracle.com> Message-ID: Hi Iris, thanks for the explanation. Seems like we have to live with this restriction :) Regards, Volker On Wed, Aug 10, 2016 at 7:06 PM, Iris Clark wrote: > Hi, Volker. > >> @Iris: do you know how auto-closing bugs on submit can be configured >> for a repository? >> >> Apparently, the CODETOOLS repository doesn't have this feature. > > That feature is not available for the hg.ojn:code-tools/* forests because > their bugs are not part of the JIRA "JDK" project (i.e. their bugs do not > begin with "JDK-".) All tools/servers which trigger a bug update based on > Hg push can only access the "JDK" project. It would be a non-trivial task > to provide such support. > > Thanks, > iris > > -----Original Message----- > From: Volker Simonis [mailto:volker.simonis at gmail.com] > Sent: Wednesday, August 10, 2016 12:39 AM > To: Staffan Larsen > Cc: code-tools-dev; Iris Clark; Jonathan Gibbons > Subject: Re: CODETOOLS-7901466 is fixed but the bug is still open ?!? > > On Wed, Aug 10, 2016 at 8:22 AM, Staffan Larsen wrote: >> >> On 9 aug. 2016, at 17:45, Volker Simonis wrote: >> >> On Tue, Aug 9, 2016 at 1:04 PM, Staffan Larsen >> wrote: >> >> >> On 9 aug. 2016, at 09:31, Volker Simonis 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. >> > > CC'ed Iris who handles such questions for our porting repositories. > > @Iris: do you know how auto-closing bugs on submit can be configured for a repository? > > Apparently, the CODETOOLS repository doesn't have this feature. > > I think, aside from the technical realization, this feature has to be requested by the corresponding project lead, so I've also CC'ed Jonathan. > > Regards, > Volker > >> /Staffan >> >> >> /Staffan >> >> >> Regards, >> Volker >> >> From jonathan.gibbons at oracle.com Thu Aug 11 02:29:40 2016 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Wed, 10 Aug 2016 19:29:40 -0700 Subject: CODETOOLS-7901466 is fixed but the bug is still open ?!? In-Reply-To: References: <42A4A273-BB65-45F1-A900-15819AA149EB@oracle.com> Message-ID: <57ABE314.5070404@oracle.com> I have marked these two issue Closed 6 months ago jlaskey 7901582: webrev -f creates bad next links when transitioning between trees default tip 7 months ago ddehaven 7901466: Mercurial 3.4 breaks behavior of webrev -r -- Jon On 08/10/2016 10:36 AM, Volker Simonis wrote: > Hi Iris, > > thanks for the explanation. > Seems like we have to live with this restriction :) > > Regards, > Volker > > > On Wed, Aug 10, 2016 at 7:06 PM, Iris Clark wrote: >> Hi, Volker. >> >>> @Iris: do you know how auto-closing bugs on submit can be configured >>> for a repository? >>> >>> Apparently, the CODETOOLS repository doesn't have this feature. >> That feature is not available for the hg.ojn:code-tools/* forests because >> their bugs are not part of the JIRA "JDK" project (i.e. their bugs do not >> begin with "JDK-".) All tools/servers which trigger a bug update based on >> Hg push can only access the "JDK" project. It would be a non-trivial task >> to provide such support. >> >> Thanks, >> iris >> >> -----Original Message----- >> From: Volker Simonis [mailto:volker.simonis at gmail.com] >> Sent: Wednesday, August 10, 2016 12:39 AM >> To: Staffan Larsen >> Cc: code-tools-dev; Iris Clark; Jonathan Gibbons >> Subject: Re: CODETOOLS-7901466 is fixed but the bug is still open ?!? >> >> On Wed, Aug 10, 2016 at 8:22 AM, Staffan Larsen wrote: >>> On 9 aug. 2016, at 17:45, Volker Simonis wrote: >>> >>> On Tue, Aug 9, 2016 at 1:04 PM, Staffan Larsen >>> wrote: >>> >>> >>> On 9 aug. 2016, at 09:31, Volker Simonis 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. >>> >> CC'ed Iris who handles such questions for our porting repositories. >> >> @Iris: do you know how auto-closing bugs on submit can be configured for a repository? >> >> Apparently, the CODETOOLS repository doesn't have this feature. >> >> I think, aside from the technical realization, this feature has to be requested by the corresponding project lead, so I've also CC'ed Jonathan. >> >> Regards, >> Volker >> >>> /Staffan >>> >>> >>> /Staffan >>> >>> >>> Regards, >>> Volker >>> >>> From alexandre.iline at oracle.com Fri Aug 19 15:19:31 2016 From: alexandre.iline at oracle.com (Alexandre (Shura) Iline) Date: Fri, 19 Aug 2016 08:19:31 -0700 Subject: CodeTools proposal: Jemmy. Message-ID: <508E1F50-B5D8-41B9-A498-41B2D5EC8CF7@oracle.com> Hi, This is a proposal to add the Jemmy tool to be a part of the Code Tools Project. Jemmy, presently hosted on jemmy.java.net, is a Java library for automated UI testing. It supports AWT, Swing, JavaFX, SWT and some other UI libraries. Jemmy is not a new library - it has a long history, it has been in the open source first as a part of NetBeans tests, and later independently on java.net. Now it needs a new home. As Jemmy used for JDK testing extensively, Code Tools Project is a logical place for it. Shura From kevin.looney at oracle.com Fri Aug 19 15:27:07 2016 From: kevin.looney at oracle.com (Kevin Looney) Date: Fri, 19 Aug 2016 08:27:07 -0700 Subject: CodeTools proposal: Jemmy. In-Reply-To: <508E1F50-B5D8-41B9-A498-41B2D5EC8CF7@oracle.com> References: <508E1F50-B5D8-41B9-A498-41B2D5EC8CF7@oracle.com> Message-ID: Jemmy is a quite useful UI testing framework, and CodeTools would make a good home for Jemmy. I'd second Shura's proposal - Yes. Kevin L On 8/19/16 8:19 AM, Alexandre (Shura) Iline wrote: > Hi, > > This is a proposal to add the Jemmy tool to be a part of the Code Tools Project. > > Jemmy, presently hosted on jemmy.java.net, is a Java library for automated UI testing. It supports AWT, Swing, JavaFX, SWT and some other UI libraries. > > Jemmy is not a new library - it has a long history, it has been in the open source first as a part of NetBeans tests, and later independently on java.net. Now it needs a new home. > > As Jemmy used for JDK testing extensively, Code Tools Project is a logical place for it. > > Shura > -- kevin.looney at oracle.com From Brian.Kurotsuchi at Oracle.COM Fri Aug 19 18:48:15 2016 From: Brian.Kurotsuchi at Oracle.COM (Brian Kurotsuchi) Date: Fri, 19 Aug 2016 12:48:15 -0600 Subject: CodeTools proposal: Jemmy. In-Reply-To: References: <508E1F50-B5D8-41B9-A498-41B2D5EC8CF7@oracle.com> Message-ID: <3bdd7ec7-cd70-c1d0-b7ea-16c125b0953c@Oracle.COM> I agree, Jemmy is useful and shouldn't be lost. On 8/19/16 9:27 AM, Kevin Looney wrote: > Jemmy is a quite useful UI testing framework, and CodeTools would make > a good home for Jemmy. > > I'd second Shura's proposal - Yes. > > Kevin L > > On 8/19/16 8:19 AM, Alexandre (Shura) Iline wrote: >> Hi, >> >> This is a proposal to add the Jemmy tool to be a part of the Code >> Tools Project. >> >> Jemmy, presently hosted on jemmy.java.net, is a Java library for >> automated UI testing. It supports AWT, Swing, JavaFX, SWT and some >> other UI libraries. >> >> Jemmy is not a new library - it has a long history, it has been in >> the open source first as a part of NetBeans tests, and later >> independently on java.net. Now it needs a new home. >> >> As Jemmy used for JDK testing extensively, Code Tools Project is a >> logical place for it. >> >> Shura >> > > From jonathan.gibbons at oracle.com Fri Aug 26 01:28:21 2016 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 25 Aug 2016 18:28:21 -0700 Subject: CodeTools proposal: Jemmy. In-Reply-To: <508E1F50-B5D8-41B9-A498-41B2D5EC8CF7@oracle.com> References: <508E1F50-B5D8-41B9-A498-41B2D5EC8CF7@oracle.com> Message-ID: <57BF9B35.1050804@oracle.com> Hi Shura, Sounds good; let's move this along. -- Jon On 08/19/2016 08:19 AM, Alexandre (Shura) Iline wrote: > Hi, > > This is a proposal to add the Jemmy tool to be a part of the Code Tools Project. > > Jemmy, presently hosted on jemmy.java.net, is a Java library for automated UI testing. It supports AWT, Swing, JavaFX, SWT and some other UI libraries. > > Jemmy is not a new library - it has a long history, it has been in the open source first as a part of NetBeans tests, and later independently on java.net. Now it needs a new home. > > As Jemmy used for JDK testing extensively, Code Tools Project is a logical place for it. > > Shura >