SigTest Tool

[Martijn Verburg]

Hi Dmitry,

I've added you to both, GitHub permissions may not let you create a repo -
if you get blocked, let me know!

Cheers,
Martijn


On 16 July 2014 09:46, Dmitry Buzdin <buzdin at gmail.com> wrote:

> Hi Martijn,
>
> I am fine with that.
>
> Could you please add me to AdoptOpenJDK GitHub group. My account is
> 'buzdin'. Access to CloubBees Jenkins is also required.
> Also, could someone confirm that the up to date location of SigTest
> sources is this one http://hg.openjdk.java.net/code-tools/sigtest
>
> So the main ideas are working on build scripts and API of existing code
> with the goal to author a custom SigTest based tool in a separate
> repository.
>
> Will also send more detailed description of the concept tonight.
>
> Regards,
> Dmitry
>
>
> On Wed, Jul 16, 2014 at 11:07 AM, Martijn Verburg <
> martijnverburg at gmail.com> wrote:
>
>> Hi Kevin/All,
>>
>> CCing in the Adoption Group as there's possibly other folks interested in
>> this area.
>>
>> @Dmitry - Feel free to use the AdoptOpenJDK GitHub site to start a repo
>> with code changes until the area around licensing / contributions can be
>> cleared up.  Just license it with GPLv2 with Classpath exception so it'll
>> be easy to merge into OpenJDK proper (if allowed etc).
>>
>> Cheers,
>> Martijn
>>
>>
>> On 15 July 2014 22:20, Kevin Looney <kevin.looney at oracle.com> wrote:
>>
>>> Hello Dima,
>>>
>>>     Your idea of 'maven plugins checking @stable annotated APIs' sounds
>>> really cool!  SigTest may be a good basis for doing such a thing.
>>>
>>> I am the development manager for the group that contributed SigTest into
>>> OpenJDK/CodeTools.  I've sent out inquiries to the engineer that develops
>>> SigTest, and someone in LUG associated with adopt-openjdk -  we'll get a
>>> few answers for you soon.
>>>
>>> I just wanted to point your attention to a couple of things. It might be
>>> possible to override SigTest logic to do what you wish - without changing
>>> the OS source. SigTest is designed in a way such that users can write
>>> 'plugins' that may implement and report incompatibilities according to
>>> their own logic.
>>>
>>> The SigTest User Guide is posted online: (http://docs.oracle.com/
>>> javame/test-tools/sigtest/3_0/html/toc.htm)
>>>
>>> Please refer to these appendices:
>>>
>>> Appendix C
>>> http://docs.oracle.com/javame/test-tools/sigtest/3_0/html/a_
>>> compat.htm#Z4000c521043455
>>>
>>> These are the rules by which SigTest currently operates, according to
>>> the Java compatibility rules defined by the JLS (chapter 3).
>>>
>>> Appendix G
>>>
>>> http://docs.oracle.com/javame/test-tools/sigtest/3_0/html/a_
>>> serialization_example.htm#CIABEGJC
>>>
>>> This is a custom-tool written using SigTest as a framework.  There is
>>> example code in the SigTest distribution that implements this tool example.
>>>  This might be a good starting point for implementing your own logic.
>>>
>>>
>>> I hope this helps.  More answers on your direct requests soon.
>>>
>>> Thanks,
>>> Kevin L
>>>
>>>
>>>
>>>
>>> On 7/15/14, 12:47 PM, Dmitry Buzdin wrote:
>>>
>>>> Hello,
>>>>
>>>> I am looking for a right person to get in touch with regards to SigTest
>>>> tool development?
>>>>
>>>> https://wiki.openjdk.java.net/display/CodeTools/sigtest
>>>>
>>>> The project I am working on would benefit greatly from that, but there
>>>> are
>>>> certain API extensibility issues and the whole build process and
>>>> publishing
>>>> to Maven Central is basically absent.
>>>> After move to Mercurial Jenkins was not reconfigured etc. etc.
>>>>
>>>> I have possibility to contribute, but need help from someone with commit
>>>> rights and idea of what is going on.
>>>>
>>>> Suggestions are:
>>>> - start publishing to Maven Central (via Bintray or directly)
>>>> - Work on API to ensure violation levels are configurable (so error
>>>> could
>>>> be substituted by warning in some projects via configuration file or
>>>> system
>>>> property)
>>>> - Reconfigure Jenkins Job on cloudbees so it runs smoothly from new
>>>> repo (
>>>> https://adopt-openjdk.ci.cloudbees.com/job/sigtest/)
>>>>
>>>> The ultimate goal is to treat SigTest as a low-level core library and
>>>> start
>>>> building proper maven plugins, which would analyse API changes, but
>>>> only in
>>>> certain packages and classes annotated as @Stable. This would be quite a
>>>> convenient tool for any build pipeline of mature framework.
>>>>
>>>> I can share more details about the approach, but the first thing is to
>>>> help
>>>> getting it to Maven repo and fix closed API restriction.
>>>>
>>>> Regards,
>>>> Dmitry Buzdin
>>>> JUG Latvia Lead
>>>>
>>>
>>>
>>> --
>>> kevin.looney at oracle.com
>>>
>>>
>>
>