SigTest Tool

[Dmitry Buzdin]

Hi,

We are in touch with Mikhail to prototype the maven plugin and see if any
modifications needed on SigTest side.

Once the prototype is there we could publish it under AdoptOpenJDK brand if
everybody is ok with that. I will let you know about the progress soon
enough.

Regards,
Dmitry


On Fri, Jul 18, 2014 at 12:18 PM, Martijn Verburg <martijnverburg at gmail.com>
wrote:

> Hi Mani,
>
> I think the Maven thing will be find.  Initially we're using
> org.adoptopenjdk - but *if* and when projects migrate to OpenJDK proper I
> assume some sort of official naming structure will be used, probably taking
> guidance from Jigsaw.
>
> Cheers,
> Martijn
>
>
> On 17 July 2014 22:56, Mani Sarkar <sadhak001 at gmail.com> wrote:
>
> > Hi Dmitry,
> >
> > Thanks for letting us know about the build, it fixed and running fine
> again
> > - do you have another repo in mind when you say new repo in your message?
> >
> > Maven plugin would be interesting to see coming out it of this tool. From
> > other messages I see Martijn has already given you access to the github
> > repo to make your contributions - looking forward to it.
> >
> > About publishing artefacts of SigTest to Maven central - I would leave
> this
> > question open to discussion - @Martijn, @Kevin, @Jonathan - what do you
> > have in mind about this, Maven Central has a set of rules that we must
> > comply to in order to publish artefacts (see
> > http://maven.apache.org/guides/mini/guide-central-repository-upload.html
> ),
> > including changing the format of the artefact name.
> >
> > If we go that route for SigTest should we also do it for other opensource
> > code-tool projects like jtreg, jtharness and jcov?
> >
> > Cheers,
> > Mani
> >
> > ------------------------------
> > >
> > > Message: 6
> > > Date: Tue, 15 Jul 2014 22:47:57 +0300
> > > From: Dmitry Buzdin <buzdin at gmail.com>
> > > To: code-tools-dev at openjdk.java.net
> > > Subject: SigTest Tool
> > > Message-ID:
> > >         <
> > > CAEwpzzwWhMgWx+p1-CB3ffC72hK1debejyqs8Mz1dNHi6Ye1Zg at mail.gmail.com>
> > > Content-Type: text/plain; charset=UTF-8
> > >
> > > 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
> > >
> > >
> > > ------------------------------
> > >
> >
> > --
> > @theNeomatrix369 <http://twitter.com/theNeomatrix369>*  |  **Blog
> > <http://neomatrix369.wordpress.com>**  |  *LJC Associate & LJC Advocate
> > (@adoptopenjdk & @adoptajsr programs)
> > *Meet-a-Project - *MutabilityDetector
> > <https://github.com/MutabilityDetector>*  |  **Bitbucket
> > <https://bitbucket.org/neomatrix369>* * |  **Github
> > <https://github.com/neomatrix369>* * |  **LinkedIn
> > <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
> > *Come to Devoxx UK 2014:* http://www.devoxx.co.uk/
> >
> > *Don't chase success, rather aim for "Excellence", and success will come
> > chasing after you!*
> >
>