From magnus.ihse.bursie at oracle.com Tue Mar 7 13:47:53 2017 From: magnus.ihse.bursie at oracle.com (Magnus Ihse Bursie) Date: Tue, 7 Mar 2017 14:47:53 +0100 Subject: RFR: CODETOOLS-7901819 hg tstatus does not work well with pager In-Reply-To: References: <3bc24d93-b3ca-b637-a64a-222a06fd5547@oracle.com> <494517750.79678.1479927110332@privateemail.com> <6d4030ad-0bbc-c549-df68-0fa34e42ef87@oracle.com> Message-ID: On 2017-01-16 14:24, Magnus Ihse Bursie wrote: > > On 2016-12-07 13:53, Magnus Ihse Bursie wrote: >> On 2016-11-23 19:51, John Coomes wrote: >>>> On November 23, 2016 at 1:16 AM Magnus Ihse Bursie >>>> wrote: >>>> >>>> Any reviewers on this? >>> Hi Magnus, >>> >>> I think it's better to call ui.flush() after running a command to >>> get the right ordering. The patch below does that in both >>> _docmd1() and _docmd2(). Feel free to push w/me as reviewer. >> >> I tried that but I do still not have write access to the hg repo. :-( Can anyone with reviewer status please push this fix? Also, can anyone with the correct status try to make me a reviewer so simple patches just don't get stuck for months upon months? The criteria for getting the proper authorization in these simple tools project should be much lower than the jdk projects. If there's a formal problem, can someone point it out to me so we can work on getting that fixed? /Magnus From gunnar at hibernate.org Wed Mar 22 09:59:40 2017 From: gunnar at hibernate.org (Gunnar Morling) Date: Wed, 22 Mar 2017 10:59:40 +0100 Subject: Where to find authoritative release of SigTest? Message-ID: Hi, I'm looking for an authoritative release of the SigTest tool. More specifically, what is the latest stable version and where can I download it? [1] mentions a "3.0 Milestone Release (March 4, 2014)" but I can't seem to find that. The "Released" link on the same page points to a CI job which apparently re-builds version 3.1 regularly. [2] provides a "3.0 dev binary bundle" from April 2013. Any pointers on where to find the latest stable version would be highly appreciated. Btw. I also learned about the "sigtest-maven-plugin" maintained by the NetBeans project [3], which apparently has forked the SigTest sources. It'd be great to have an official release of the original project in Maven Central, so that it can be consumed by this plug-in and other users. Thanks, --Gunnar [1] https://wiki.openjdk.java.net/display/CodeTools/sigtest [2] http://download.java.net/sigtest/download.html [3] http://wiki.netbeans.org/SigTest From Mikhail.Ershov at oracle.com Wed Mar 22 11:18:14 2017 From: Mikhail.Ershov at oracle.com (Mikhail Ershov) Date: Wed, 22 Mar 2017 14:18:14 +0300 Subject: Where to find authoritative release of SigTest? In-Reply-To: References: Message-ID: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> Hi Gunnar, I'd recommend you to clone sources of current v4.0 and build it: >hg clone http://hg.openjdk.java.net/code-tools/sigtest >cd sigtest/build edit build.properties (you have to point to java 8 at least) >ant Maven plugin sources are there but I'm not 100% sure that this part is in a good shape and actual. You probably can try to get actual binaries built by a community here https://adopt-openjdk.ci.cloudbees.com/job/sigtest/ but unfortunately I can't point to our actual binaries. Feel free to ask any questions, Mike Ershov SigTest developer. On 22.03.2017 12:59, Gunnar Morling wrote: > Hi, > > I'm looking for an authoritative release of the SigTest tool. More > specifically, what is the latest stable version and where can I > download it? > > [1] mentions a "3.0 Milestone Release (March 4, 2014)" but I can't > seem to find that. The "Released" link on the same page points to a CI > job which apparently re-builds version 3.1 regularly. [2] provides a > "3.0 dev binary bundle" from April 2013. > > Any pointers on where to find the latest stable version would be > highly appreciated. > > Btw. I also learned about the "sigtest-maven-plugin" maintained by the > NetBeans project [3], which apparently has forked the SigTest sources. > It'd be great to have an official release of the original project in > Maven Central, so that it can be consumed by this plug-in and other > users. > > Thanks, > > --Gunnar > > [1] https://wiki.openjdk.java.net/display/CodeTools/sigtest > [2] http://download.java.net/sigtest/download.html > [3] http://wiki.netbeans.org/SigTest From gunnar at hibernate.org Wed Mar 22 11:30:53 2017 From: gunnar at hibernate.org (Gunnar Morling) Date: Wed, 22 Mar 2017 12:30:53 +0100 Subject: Where to find authoritative release of SigTest? In-Reply-To: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> References: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> Message-ID: Hi Mikhail, Thanks for your quick reply. > I'd recommend you to clone sources of current v4.0 Building from source is very impractical for any project seeking to incorporate SigTest into their build. > You probably can try to get actual binaries built by a community here Yes, but that's a moving target really. It seems to re-build the "3.1" version with each run, so it's nothing stable to rely on. Can you do a release of SigTest to Maven Central? That way there will be a proper release of a defined version of the code base, and it's easily consumable for users (as well as the mentioned Maven plug-in maintained by the NetBeans team). SigTest is such a useful tool - e.g. the Bean Validation spec is using it for checking API compliance of providers - but in its current form it's unfortunately close to impossible to use it in a repeatable, automated way. Having it in Maven Central would greatly change that. Thanks, --Gunnar 2017-03-22 12:18 GMT+01:00 Mikhail Ershov : > Hi Gunnar, > > I'd recommend you to clone sources of current v4.0 and build it: > >>hg clone http://hg.openjdk.java.net/code-tools/sigtest >>cd sigtest/build > edit build.properties (you have to point to java 8 at least) >>ant > > Maven plugin sources are there but I'm not 100% sure that this part is in a > good shape and actual. > > You probably can try to get actual binaries built by a community here > https://adopt-openjdk.ci.cloudbees.com/job/sigtest/ but unfortunately I > can't point to our actual binaries. > > Feel free to ask any questions, > > Mike Ershov > SigTest developer. > > > On 22.03.2017 12:59, Gunnar Morling wrote: >> >> Hi, >> >> I'm looking for an authoritative release of the SigTest tool. More >> specifically, what is the latest stable version and where can I >> download it? >> >> [1] mentions a "3.0 Milestone Release (March 4, 2014)" but I can't >> seem to find that. The "Released" link on the same page points to a CI >> job which apparently re-builds version 3.1 regularly. [2] provides a >> "3.0 dev binary bundle" from April 2013. >> >> Any pointers on where to find the latest stable version would be >> highly appreciated. >> >> Btw. I also learned about the "sigtest-maven-plugin" maintained by the >> NetBeans project [3], which apparently has forked the SigTest sources. >> It'd be great to have an official release of the original project in >> Maven Central, so that it can be consumed by this plug-in and other >> users. >> >> Thanks, >> >> --Gunnar >> >> [1] https://wiki.openjdk.java.net/display/CodeTools/sigtest >> [2] http://download.java.net/sigtest/download.html >> [3] http://wiki.netbeans.org/SigTest > > From martijnverburg at gmail.com Wed Mar 22 15:01:37 2017 From: martijnverburg at gmail.com (Martijn Verburg) Date: Wed, 22 Mar 2017 15:01:37 +0000 Subject: Where to find authoritative release of SigTest? In-Reply-To: References: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> Message-ID: Hi all, We (https://adopt-openjdk.ci.cloudbees.com/job/sigtest/) is deliberately building the latest stable (3.1) binary. Happy to add another job to build and produce a nightly build based on the latest source if that helps? CCing in the adoption-discuss list as that's where Mani and other folks who manage that discuss these things. Cheers, Martijn On 22 March 2017 at 11:30, Gunnar Morling wrote: > Hi Mikhail, > > Thanks for your quick reply. > >> I'd recommend you to clone sources of current v4.0 > > Building from source is very impractical for any project seeking to > incorporate SigTest into their build. > >> You probably can try to get actual binaries built by a community here > > Yes, but that's a moving target really. It seems to re-build the "3.1" > version with each run, so it's nothing stable to rely on. > > Can you do a release of SigTest to Maven Central? That way there will > be a proper release of a defined version of the code base, and it's > easily consumable for users (as well as the mentioned Maven plug-in > maintained by the NetBeans team). > > SigTest is such a useful tool - e.g. the Bean Validation spec is using > it for checking API compliance of providers - but in its current form > it's unfortunately close to impossible to use it in a repeatable, > automated way. > > Having it in Maven Central would greatly change that. > > Thanks, > > --Gunnar > > > > > > 2017-03-22 12:18 GMT+01:00 Mikhail Ershov : >> Hi Gunnar, >> >> I'd recommend you to clone sources of current v4.0 and build it: >> >>>hg clone http://hg.openjdk.java.net/code-tools/sigtest >>>cd sigtest/build >> edit build.properties (you have to point to java 8 at least) >>>ant >> >> Maven plugin sources are there but I'm not 100% sure that this part is in a >> good shape and actual. >> >> You probably can try to get actual binaries built by a community here >> https://adopt-openjdk.ci.cloudbees.com/job/sigtest/ but unfortunately I >> can't point to our actual binaries. >> >> Feel free to ask any questions, >> >> Mike Ershov >> SigTest developer. >> >> >> On 22.03.2017 12:59, Gunnar Morling wrote: >>> >>> Hi, >>> >>> I'm looking for an authoritative release of the SigTest tool. More >>> specifically, what is the latest stable version and where can I >>> download it? >>> >>> [1] mentions a "3.0 Milestone Release (March 4, 2014)" but I can't >>> seem to find that. The "Released" link on the same page points to a CI >>> job which apparently re-builds version 3.1 regularly. [2] provides a >>> "3.0 dev binary bundle" from April 2013. >>> >>> Any pointers on where to find the latest stable version would be >>> highly appreciated. >>> >>> Btw. I also learned about the "sigtest-maven-plugin" maintained by the >>> NetBeans project [3], which apparently has forked the SigTest sources. >>> It'd be great to have an official release of the original project in >>> Maven Central, so that it can be consumed by this plug-in and other >>> users. >>> >>> Thanks, >>> >>> --Gunnar >>> >>> [1] https://wiki.openjdk.java.net/display/CodeTools/sigtest >>> [2] http://download.java.net/sigtest/download.html >>> [3] http://wiki.netbeans.org/SigTest >> >> From sadhak001 at gmail.com Wed Mar 22 15:10:16 2017 From: sadhak001 at gmail.com (Mani Sarkar) Date: Wed, 22 Mar 2017 15:10:16 +0000 Subject: Where to find authoritative release of SigTest? In-Reply-To: References: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> Message-ID: Hi Gunnar, Please send details of any other related project that need their binary produced and hosted on our farm just like the existing ones. We will try to get them setup for the community. Cheers, Mani On Wed, 22 Mar 2017 at 15:02 Martijn Verburg wrote: > Hi all, > > We (https://adopt-openjdk.ci.cloudbees.com/job/sigtest/) is > deliberately building the latest stable (3.1) binary. Happy to add > another job to build and produce a nightly build based on the latest > source if that helps? > > CCing in the adoption-discuss list as that's where Mani and other > folks who manage that discuss these things. > Cheers, > Martijn > > > On 22 March 2017 at 11:30, Gunnar Morling wrote: > > Hi Mikhail, > > > > Thanks for your quick reply. > > > >> I'd recommend you to clone sources of current v4.0 > > > > Building from source is very impractical for any project seeking to > > incorporate SigTest into their build. > > > >> You probably can try to get actual binaries built by a community here > > > > Yes, but that's a moving target really. It seems to re-build the "3.1" > > version with each run, so it's nothing stable to rely on. > > > > Can you do a release of SigTest to Maven Central? That way there will > > be a proper release of a defined version of the code base, and it's > > easily consumable for users (as well as the mentioned Maven plug-in > > maintained by the NetBeans team). > > > > SigTest is such a useful tool - e.g. the Bean Validation spec is using > > it for checking API compliance of providers - but in its current form > > it's unfortunately close to impossible to use it in a repeatable, > > automated way. > > > > Having it in Maven Central would greatly change that. > > > > Thanks, > > > > --Gunnar > > > > > > > > > > > > 2017-03-22 12:18 GMT+01:00 Mikhail Ershov : > >> Hi Gunnar, > >> > >> I'd recommend you to clone sources of current v4.0 and build it: > >> > >>>hg clone http://hg.openjdk.java.net/code-tools/sigtest > >>>cd sigtest/build > >> edit build.properties (you have to point to java 8 at least) > >>>ant > >> > >> Maven plugin sources are there but I'm not 100% sure that this part is > in a > >> good shape and actual. > >> > >> You probably can try to get actual binaries built by a community here > >> https://adopt-openjdk.ci.cloudbees.com/job/sigtest/ but unfortunately I > >> can't point to our actual binaries. > >> > >> Feel free to ask any questions, > >> > >> Mike Ershov > >> SigTest developer. > >> > >> > >> On 22.03.2017 12:59, Gunnar Morling wrote: > >>> > >>> Hi, > >>> > >>> I'm looking for an authoritative release of the SigTest tool. More > >>> specifically, what is the latest stable version and where can I > >>> download it? > >>> > >>> [1] mentions a "3.0 Milestone Release (March 4, 2014)" but I can't > >>> seem to find that. The "Released" link on the same page points to a CI > >>> job which apparently re-builds version 3.1 regularly. [2] provides a > >>> "3.0 dev binary bundle" from April 2013. > >>> > >>> Any pointers on where to find the latest stable version would be > >>> highly appreciated. > >>> > >>> Btw. I also learned about the "sigtest-maven-plugin" maintained by the > >>> NetBeans project [3], which apparently has forked the SigTest sources. > >>> It'd be great to have an official release of the original project in > >>> Maven Central, so that it can be consumed by this plug-in and other > >>> users. > >>> > >>> Thanks, > >>> > >>> --Gunnar > >>> > >>> [1] https://wiki.openjdk.java.net/display/CodeTools/sigtest > >>> [2] http://download.java.net/sigtest/download.html > >>> [3] http://wiki.netbeans.org/SigTest > >> > >> > -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2017:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* From gunnar at hibernate.org Wed Mar 22 15:34:15 2017 From: gunnar at hibernate.org (Gunnar Morling) Date: Wed, 22 Mar 2017 16:34:15 +0100 Subject: Where to find authoritative release of SigTest? In-Reply-To: References: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> Message-ID: Hi Martijn, Thanks for chiming in. The CI job is cool, but it's not a good source for obtaining a stable artifact. While it seems to re-build the same tag again and again, the produced artifact may change over time. Let's say Java on that CI server gets updated, then the produced bytecode may be a tad different. I.e. different people may end up with up with different versions of "SigTest 3.1", making it very hard to analyse any problems. Taking an artifact from such rather volatile location generally isn't great for a repeatable build of downstream consumers nor is it something I'd like to recommend to users of the Bean Validation TCK (which is where we are using it for). For consumers such as Bean Validation it'd be great if that 3.1 release could be deployed to Maven Central. Then we had one canonical version of it which we can consume it in a repeatable way using standard build procedures. Cheers, --Gunnar 2017-03-22 16:01 GMT+01:00 Martijn Verburg : > Hi all, > > We (https://adopt-openjdk.ci.cloudbees.com/job/sigtest/) is > deliberately building the latest stable (3.1) binary. Happy to add > another job to build and produce a nightly build based on the latest > source if that helps? > > CCing in the adoption-discuss list as that's where Mani and other > folks who manage that discuss these things. > Cheers, > Martijn > > > On 22 March 2017 at 11:30, Gunnar Morling wrote: >> Hi Mikhail, >> >> Thanks for your quick reply. >> >>> I'd recommend you to clone sources of current v4.0 >> >> Building from source is very impractical for any project seeking to >> incorporate SigTest into their build. >> >>> You probably can try to get actual binaries built by a community here >> >> Yes, but that's a moving target really. It seems to re-build the "3.1" >> version with each run, so it's nothing stable to rely on. >> >> Can you do a release of SigTest to Maven Central? That way there will >> be a proper release of a defined version of the code base, and it's >> easily consumable for users (as well as the mentioned Maven plug-in >> maintained by the NetBeans team). >> >> SigTest is such a useful tool - e.g. the Bean Validation spec is using >> it for checking API compliance of providers - but in its current form >> it's unfortunately close to impossible to use it in a repeatable, >> automated way. >> >> Having it in Maven Central would greatly change that. >> >> Thanks, >> >> --Gunnar >> >> >> >> >> >> 2017-03-22 12:18 GMT+01:00 Mikhail Ershov : >>> Hi Gunnar, >>> >>> I'd recommend you to clone sources of current v4.0 and build it: >>> >>>>hg clone http://hg.openjdk.java.net/code-tools/sigtest >>>>cd sigtest/build >>> edit build.properties (you have to point to java 8 at least) >>>>ant >>> >>> Maven plugin sources are there but I'm not 100% sure that this part is in a >>> good shape and actual. >>> >>> You probably can try to get actual binaries built by a community here >>> https://adopt-openjdk.ci.cloudbees.com/job/sigtest/ but unfortunately I >>> can't point to our actual binaries. >>> >>> Feel free to ask any questions, >>> >>> Mike Ershov >>> SigTest developer. >>> >>> >>> On 22.03.2017 12:59, Gunnar Morling wrote: >>>> >>>> Hi, >>>> >>>> I'm looking for an authoritative release of the SigTest tool. More >>>> specifically, what is the latest stable version and where can I >>>> download it? >>>> >>>> [1] mentions a "3.0 Milestone Release (March 4, 2014)" but I can't >>>> seem to find that. The "Released" link on the same page points to a CI >>>> job which apparently re-builds version 3.1 regularly. [2] provides a >>>> "3.0 dev binary bundle" from April 2013. >>>> >>>> Any pointers on where to find the latest stable version would be >>>> highly appreciated. >>>> >>>> Btw. I also learned about the "sigtest-maven-plugin" maintained by the >>>> NetBeans project [3], which apparently has forked the SigTest sources. >>>> It'd be great to have an official release of the original project in >>>> Maven Central, so that it can be consumed by this plug-in and other >>>> users. >>>> >>>> Thanks, >>>> >>>> --Gunnar >>>> >>>> [1] https://wiki.openjdk.java.net/display/CodeTools/sigtest >>>> [2] http://download.java.net/sigtest/download.html >>>> [3] http://wiki.netbeans.org/SigTest >>> >>> From sadhak001 at gmail.com Thu Mar 23 16:35:30 2017 From: sadhak001 at gmail.com (Mani Sarkar) Date: Thu, 23 Mar 2017 16:35:30 +0000 Subject: Where to find authoritative release of SigTest? In-Reply-To: References: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> Message-ID: Hi Gunnar, I'm not speaking on behalf of Martijn (he will come back with his part), but whatever I'll say comes from my experiences contributing to our community. Its great feedback you have come back with, could you give me bullet pointed-set-of constructive actions that we can work on (in agreement with our adopt + build farm folks). I can always create an additional downloadable tar-ball (from the build farm) which complies with your suggestion for version (at least include the JDK version). We could also try to capture some system information about the environment we build the artifact in and include it in the tarball for posterity reasons. If this works for you, please let us know. Thanks. Cheers Mani -------- Response to message from the digest --- Message: 6 Date: Wed, 22 Mar 2017 16:34:15 +0100 From: Gunnar Morling To: Martijn Verburg Cc: code-tools-dev at openjdk.java.net, "adoption-discuss at openjdk.java.net" Subject: Re: Where to find authoritative release of SigTest? Message-ID: Content-Type: text/plain; charset=UTF-8 Hi Martijn, Thanks for chiming in. The CI job is cool, but it's not a good source for obtaining a stable artifact. While it seems to re-build the same tag again and again, the produced artifact may change over time. Let's say Java on that CI server gets updated, then the produced bytecode may be a tad different. I.e. different people may end up with up with different versions of "SigTest 3.1", making it very hard to analyse any problems. Taking an artifact from such rather volatile location generally isn't great for a repeatable build of downstream consumers nor is it something I'd like to recommend to users of the Bean Validation TCK (which is where we are using it for). For consumers such as Bean Validation it'd be great if that 3.1 release could be deployed to Maven Central. Then we had one canonical version of it which we can consume it in a repeatable way using standard build procedures. Cheers, --Gunnar On Wed, 22 Mar 2017 at 15:10 Mani Sarkar wrote: > Hi Gunnar, > > Please send details of any other related project that need their binary > produced and hosted on our farm just like the existing ones. > > We will try to get them setup for the community. > > Cheers, > Mani > > On Wed, 22 Mar 2017 at 15:02 Martijn Verburg > wrote: > > Hi all, > > We (https://adopt-openjdk.ci.cloudbees.com/job/sigtest/) is > deliberately building the latest stable (3.1) binary. Happy to add > another job to build and produce a nightly build based on the latest > source if that helps? > > CCing in the adoption-discuss list as that's where Mani and other > folks who manage that discuss these things. > Cheers, > Martijn > > > On 22 March 2017 at 11:30, Gunnar Morling wrote: > > Hi Mikhail, > > > > Thanks for your quick reply. > > > >> I'd recommend you to clone sources of current v4.0 > > > > Building from source is very impractical for any project seeking to > > incorporate SigTest into their build. > > > >> You probably can try to get actual binaries built by a community here > > > > Yes, but that's a moving target really. It seems to re-build the "3.1" > > version with each run, so it's nothing stable to rely on. > > > > Can you do a release of SigTest to Maven Central? That way there will > > be a proper release of a defined version of the code base, and it's > > easily consumable for users (as well as the mentioned Maven plug-in > > maintained by the NetBeans team). > > > > SigTest is such a useful tool - e.g. the Bean Validation spec is using > > it for checking API compliance of providers - but in its current form > > it's unfortunately close to impossible to use it in a repeatable, > > automated way. > > > > Having it in Maven Central would greatly change that. > > > > Thanks, > > > > --Gunnar > > > > > > > > > > > > 2017-03-22 12:18 GMT+01:00 Mikhail Ershov : > >> Hi Gunnar, > >> > >> I'd recommend you to clone sources of current v4.0 and build it: > >> > >>>hg clone http://hg.openjdk.java.net/code-tools/sigtest > >>>cd sigtest/build > >> edit build.properties (you have to point to java 8 at least) > >>>ant > >> > >> Maven plugin sources are there but I'm not 100% sure that this part is > in a > >> good shape and actual. > >> > >> You probably can try to get actual binaries built by a community here > >> https://adopt-openjdk.ci.cloudbees.com/job/sigtest/ but unfortunately I > >> can't point to our actual binaries. > >> > >> Feel free to ask any questions, > >> > >> Mike Ershov > >> SigTest developer. > >> > >> > >> On 22.03.2017 12:59, Gunnar Morling wrote: > >>> > >>> Hi, > >>> > >>> I'm looking for an authoritative release of the SigTest tool. More > >>> specifically, what is the latest stable version and where can I > >>> download it? > >>> > >>> [1] mentions a "3.0 Milestone Release (March 4, 2014)" but I can't > >>> seem to find that. The "Released" link on the same page points to a CI > >>> job which apparently re-builds version 3.1 regularly. [2] provides a > >>> "3.0 dev binary bundle" from April 2013. > >>> > >>> Any pointers on where to find the latest stable version would be > >>> highly appreciated. > >>> > >>> Btw. I also learned about the "sigtest-maven-plugin" maintained by the > >>> NetBeans project [3], which apparently has forked the SigTest sources. > >>> It'd be great to have an official release of the original project in > >>> Maven Central, so that it can be consumed by this plug-in and other > >>> users. > >>> > >>> Thanks, > >>> > >>> --Gunnar > >>> > >>> [1] https://wiki.openjdk.java.net/display/CodeTools/sigtest > >>> [2] http://download.java.net/sigtest/download.html > >>> [3] http://wiki.netbeans.org/SigTest > >> > >> > > -- > @theNeomatrix369 * | **Blog > ** | *LJC Associate & LJC Advocate > (@adoptopenjdk & @adoptajsr programs) > *Meet-a-Project - *MutabilityDetector > * | **Bitbucket > * * | **Github > * * | **LinkedIn > * > *Come to Devoxx UK 2017:* http://www.devoxx.co.uk/ > > *Don't chase success, rather aim for "Excellence", and success will come > chasing after you!* > -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2017:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* From jonathan.gibbons at oracle.com Thu Mar 23 16:50:22 2017 From: jonathan.gibbons at oracle.com (Jonathan Gibbons) Date: Thu, 23 Mar 2017 09:50:22 -0700 Subject: Where to find authoritative release of SigTest? In-Reply-To: References: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> Message-ID: <8d0edd02-2a5c-60ef-47d7-8b00f3d4bbf1@oracle.com> Oracle does not publish binary builds for tools in the Code Tools family. For jtreg (another tool in the Code Tools family) we use tags to mark specific changesets for general use. In conjunction with those tags, there are then two builds that are of probable interest: * The latest version tagged with "jtreg-bNN" indicates the latest stable version that is recommended for general use for testing JDK. * The tip is the latest experimental version, and is only recommended for use when the experimental features are required. During JDK 9, this has been used to build versions of jtreg for use with the jigsaw/jake forest, prior to integrating the changes in that forest into jdk9/dev. Perhaps we could use the same or similar methodology for SigTest. -- Jon On 3/22/17 8:34 AM, Gunnar Morling wrote: > Hi Martijn, > > Thanks for chiming in. > > The CI job is cool, but it's not a good source for obtaining a stable > artifact. While it seems to re-build the same tag again and again, the > produced artifact may change over time. Let's say Java on that CI > server gets updated, then the produced bytecode may be a tad > different. I.e. different people may end up with up with different > versions of "SigTest 3.1", making it very hard to analyse any > problems. > > Taking an artifact from such rather volatile location generally isn't > great for a repeatable build of downstream consumers nor is it > something I'd like to recommend to users of the Bean Validation TCK > (which is where we are using it for). > > For consumers such as Bean Validation it'd be great if that 3.1 > release could be deployed to Maven Central. Then we had one canonical > version of it which we can consume it in a repeatable way using > standard build procedures. > > Cheers, > > --Gunnar > > > > 2017-03-22 16:01 GMT+01:00 Martijn Verburg : >> Hi all, >> >> We (https://adopt-openjdk.ci.cloudbees.com/job/sigtest/) is >> deliberately building the latest stable (3.1) binary. Happy to add >> another job to build and produce a nightly build based on the latest >> source if that helps? >> >> CCing in the adoption-discuss list as that's where Mani and other >> folks who manage that discuss these things. >> Cheers, >> Martijn >> >> >> On 22 March 2017 at 11:30, Gunnar Morling wrote: >>> Hi Mikhail, >>> >>> Thanks for your quick reply. >>> >>>> I'd recommend you to clone sources of current v4.0 >>> Building from source is very impractical for any project seeking to >>> incorporate SigTest into their build. >>> >>>> You probably can try to get actual binaries built by a community here >>> Yes, but that's a moving target really. It seems to re-build the "3.1" >>> version with each run, so it's nothing stable to rely on. >>> >>> Can you do a release of SigTest to Maven Central? That way there will >>> be a proper release of a defined version of the code base, and it's >>> easily consumable for users (as well as the mentioned Maven plug-in >>> maintained by the NetBeans team). >>> >>> SigTest is such a useful tool - e.g. the Bean Validation spec is using >>> it for checking API compliance of providers - but in its current form >>> it's unfortunately close to impossible to use it in a repeatable, >>> automated way. >>> >>> Having it in Maven Central would greatly change that. >>> >>> Thanks, >>> >>> --Gunnar >>> >>> >>> >>> >>> >>> 2017-03-22 12:18 GMT+01:00 Mikhail Ershov : >>>> Hi Gunnar, >>>> >>>> I'd recommend you to clone sources of current v4.0 and build it: >>>> >>>>> hg clone http://hg.openjdk.java.net/code-tools/sigtest >>>>> cd sigtest/build >>>> edit build.properties (you have to point to java 8 at least) >>>>> ant >>>> Maven plugin sources are there but I'm not 100% sure that this part is in a >>>> good shape and actual. >>>> >>>> You probably can try to get actual binaries built by a community here >>>> https://adopt-openjdk.ci.cloudbees.com/job/sigtest/ but unfortunately I >>>> can't point to our actual binaries. >>>> >>>> Feel free to ask any questions, >>>> >>>> Mike Ershov >>>> SigTest developer. >>>> >>>> >>>> On 22.03.2017 12:59, Gunnar Morling wrote: >>>>> Hi, >>>>> >>>>> I'm looking for an authoritative release of the SigTest tool. More >>>>> specifically, what is the latest stable version and where can I >>>>> download it? >>>>> >>>>> [1] mentions a "3.0 Milestone Release (March 4, 2014)" but I can't >>>>> seem to find that. The "Released" link on the same page points to a CI >>>>> job which apparently re-builds version 3.1 regularly. [2] provides a >>>>> "3.0 dev binary bundle" from April 2013. >>>>> >>>>> Any pointers on where to find the latest stable version would be >>>>> highly appreciated. >>>>> >>>>> Btw. I also learned about the "sigtest-maven-plugin" maintained by the >>>>> NetBeans project [3], which apparently has forked the SigTest sources. >>>>> It'd be great to have an official release of the original project in >>>>> Maven Central, so that it can be consumed by this plug-in and other >>>>> users. >>>>> >>>>> Thanks, >>>>> >>>>> --Gunnar >>>>> >>>>> [1] https://wiki.openjdk.java.net/display/CodeTools/sigtest >>>>> [2] http://download.java.net/sigtest/download.html >>>>> [3] http://wiki.netbeans.org/SigTest >>>> From gunnar at hibernate.org Fri Mar 24 11:36:28 2017 From: gunnar at hibernate.org (Gunnar Morling) Date: Fri, 24 Mar 2017 12:36:28 +0100 Subject: Where to find authoritative release of SigTest? In-Reply-To: <8d0edd02-2a5c-60ef-47d7-8b00f3d4bbf1@oracle.com> References: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> <8d0edd02-2a5c-60ef-47d7-8b00f3d4bbf1@oracle.com> Message-ID: Hi Jonathan, > Oracle does not publish binary builds for tools in the Code Tools family. Thanks for the clarification. It's a pity, though. Having SigTest and others available for consumption in Maven Central (or any other repository, or at least as a *stable* download file) would greatly improve their usability. Esp. considering that binaries of SigTest have been published in the past. I appreciate the efforts from the Adopt-OpenJDK team for providing those build jobs a lot, but that's not really a good basis for applying SigTest in a reliable and repeatable way in downstream projects. --Gunnar 2017-03-23 17:50 GMT+01:00 Jonathan Gibbons : > Oracle does not publish binary builds for tools in the Code Tools family. > > For jtreg (another tool in the Code Tools family) we use tags to mark > specific changesets for general use. > > In conjunction with those tags, there are then two builds that are of > probable interest: > > * The latest version tagged with "jtreg-bNN" indicates the latest stable > version that is recommended for general use for testing JDK. > > * The tip is the latest experimental version, and is only recommended for > use when the experimental features are required. During JDK 9, this has been > used to build versions of jtreg for use with the jigsaw/jake forest, prior > to integrating the changes in that forest into jdk9/dev. > > Perhaps we could use the same or similar methodology for SigTest. > > -- Jon > > > > > On 3/22/17 8:34 AM, Gunnar Morling wrote: >> >> Hi Martijn, >> >> Thanks for chiming in. >> >> The CI job is cool, but it's not a good source for obtaining a stable >> artifact. While it seems to re-build the same tag again and again, the >> produced artifact may change over time. Let's say Java on that CI >> server gets updated, then the produced bytecode may be a tad >> different. I.e. different people may end up with up with different >> versions of "SigTest 3.1", making it very hard to analyse any >> problems. >> >> Taking an artifact from such rather volatile location generally isn't >> great for a repeatable build of downstream consumers nor is it >> something I'd like to recommend to users of the Bean Validation TCK >> (which is where we are using it for). >> >> For consumers such as Bean Validation it'd be great if that 3.1 >> release could be deployed to Maven Central. Then we had one canonical >> version of it which we can consume it in a repeatable way using >> standard build procedures. >> >> Cheers, >> >> --Gunnar >> >> >> >> 2017-03-22 16:01 GMT+01:00 Martijn Verburg : >>> >>> Hi all, >>> >>> We (https://adopt-openjdk.ci.cloudbees.com/job/sigtest/) is >>> deliberately building the latest stable (3.1) binary. Happy to add >>> another job to build and produce a nightly build based on the latest >>> source if that helps? >>> >>> CCing in the adoption-discuss list as that's where Mani and other >>> folks who manage that discuss these things. >>> Cheers, >>> Martijn >>> >>> >>> On 22 March 2017 at 11:30, Gunnar Morling wrote: >>>> >>>> Hi Mikhail, >>>> >>>> Thanks for your quick reply. >>>> >>>>> I'd recommend you to clone sources of current v4.0 >>>> >>>> Building from source is very impractical for any project seeking to >>>> incorporate SigTest into their build. >>>> >>>>> You probably can try to get actual binaries built by a community here >>>> >>>> Yes, but that's a moving target really. It seems to re-build the "3.1" >>>> version with each run, so it's nothing stable to rely on. >>>> >>>> Can you do a release of SigTest to Maven Central? That way there will >>>> be a proper release of a defined version of the code base, and it's >>>> easily consumable for users (as well as the mentioned Maven plug-in >>>> maintained by the NetBeans team). >>>> >>>> SigTest is such a useful tool - e.g. the Bean Validation spec is using >>>> it for checking API compliance of providers - but in its current form >>>> it's unfortunately close to impossible to use it in a repeatable, >>>> automated way. >>>> >>>> Having it in Maven Central would greatly change that. >>>> >>>> Thanks, >>>> >>>> --Gunnar >>>> >>>> >>>> >>>> >>>> >>>> 2017-03-22 12:18 GMT+01:00 Mikhail Ershov : >>>>> >>>>> Hi Gunnar, >>>>> >>>>> I'd recommend you to clone sources of current v4.0 and build it: >>>>> >>>>>> hg clone http://hg.openjdk.java.net/code-tools/sigtest >>>>>> cd sigtest/build >>>>> >>>>> edit build.properties (you have to point to java 8 at least) >>>>>> >>>>>> ant >>>>> >>>>> Maven plugin sources are there but I'm not 100% sure that this part is >>>>> in a >>>>> good shape and actual. >>>>> >>>>> You probably can try to get actual binaries built by a community here >>>>> https://adopt-openjdk.ci.cloudbees.com/job/sigtest/ but unfortunately I >>>>> can't point to our actual binaries. >>>>> >>>>> Feel free to ask any questions, >>>>> >>>>> Mike Ershov >>>>> SigTest developer. >>>>> >>>>> >>>>> On 22.03.2017 12:59, Gunnar Morling wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> I'm looking for an authoritative release of the SigTest tool. More >>>>>> specifically, what is the latest stable version and where can I >>>>>> download it? >>>>>> >>>>>> [1] mentions a "3.0 Milestone Release (March 4, 2014)" but I can't >>>>>> seem to find that. The "Released" link on the same page points to a CI >>>>>> job which apparently re-builds version 3.1 regularly. [2] provides a >>>>>> "3.0 dev binary bundle" from April 2013. >>>>>> >>>>>> Any pointers on where to find the latest stable version would be >>>>>> highly appreciated. >>>>>> >>>>>> Btw. I also learned about the "sigtest-maven-plugin" maintained by the >>>>>> NetBeans project [3], which apparently has forked the SigTest sources. >>>>>> It'd be great to have an official release of the original project in >>>>>> Maven Central, so that it can be consumed by this plug-in and other >>>>>> users. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> --Gunnar >>>>>> >>>>>> [1] https://wiki.openjdk.java.net/display/CodeTools/sigtest >>>>>> [2] http://download.java.net/sigtest/download.html >>>>>> [3] http://wiki.netbeans.org/SigTest >>>>> >>>>> > From dalibor.topic at oracle.com Tue Mar 28 12:27:30 2017 From: dalibor.topic at oracle.com (dalibor topic) Date: Tue, 28 Mar 2017 14:27:30 +0200 Subject: Where to find authoritative release of SigTest? In-Reply-To: References: <050e512b-3974-333e-13a6-d3b2caf855ca@oracle.com> <8d0edd02-2a5c-60ef-47d7-8b00f3d4bbf1@oracle.com> Message-ID: <93409aa5-4e41-7f93-8d4a-6851cb289783@oracle.com> On 24.03.2017 12:36, Gunnar Morling wrote: > It's a pity, though. Having SigTest and others available for > consumption in Maven Central (or any other repository, or at least as > a *stable* download file) would greatly improve their usability. A popular way to contribute to many open source projects is to 'package' them for consumption in various venues according to different conventions. While Oracle doesn't publish binary builds (or push them to Maven, or what have you), if someone else needs such artifacts, they could arrange to publish them. In the ideal case, they'd even attempt to coordinate with the upstream project. ;) cheers, dalibor topic -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Jan Schultheiss, Val Maher Oracle is committed to developing practices and products that help protect the environment