Where to find authoritative release of SigTest?

[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 <martijnverburg at gmail.com>:
>> 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 <gunnar at hibernate.org> 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 <Mikhail.Ershov at 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
>>>>