martijnverburg at gmail.com
Wed Jul 16 08:07:38 UTC 2014
CCing in the Adoption Group as there's possibly other folks interested in
@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).
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/
> Please refer to these appendices:
> Appendix C
> These are the rules by which SigTest currently operates, according to the
> Java compatibility rules defined by the JLS (chapter 3).
> Appendix G
> 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.
> Kevin L
> On 7/15/14, 12:47 PM, Dmitry Buzdin wrote:
>> I am looking for a right person to get in touch with regards to SigTest
>> tool development?
>> The project I am working on would benefit greatly from that, but there are
>> certain API extensibility issues and the whole build process and
>> 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
>> - Reconfigure Jenkins Job on cloudbees so it runs smoothly from new repo (
>> The ultimate goal is to treat SigTest as a low-level core library and
>> building proper maven plugins, which would analyse API changes, but only
>> 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
>> getting it to Maven repo and fix closed API restriction.
>> Dmitry Buzdin
>> JUG Latvia Lead
> kevin.looney at oracle.com
More information about the adoption-discuss