maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marco Vermeulen <vermeulen...@gmail.com>
Subject Re: Inclusion of Maven on SDKMAN
Date Sun, 13 Dec 2015 19:35:15 GMT
Hi Hervé,

Apologies for the delayed reply.

Regarding Jenkins and SDKMAN, they really operate very differently.
Unfortunately, I currently have no plans to make SDKMAN more like Jenkins.
Jenkins is a CI server, and SDKMAN is a package manager.

SDKMAN has a client side tool (bash CLI) that calls to a serverside REST
API. This API tells the client side:

a) what versions are available for a given candidate [1]
b) what the current stable version is for that candidate [2]

These are simple API calls that you could use too as part of your release.
Doing these API calls could be done with curl, and you need not install
SDKMAN to get this information. The API is free to use, and open, as the
rest of SDKMAN is.

Of course, these API calls are not to be confused with those exposed in the
Vendor API that parties like yourselves will use to perform their releases
on our platform.

Regarding API keys for the Vendor API, these are issued on an
organisational level at the moment, each vendor receiving a key/token pair
to use as part of their release process.

Hope this answers most of your questions above.

Cheers,
Marco.

[1] http://api.sdkman.io/candidates/maven
[2] http://api.sdkman.io/candidates/maven/default




On Wed, 9 Dec 2015 at 15:37 Hervé BOUTEMY <herve.boutemy@free.fr> wrote:

> yes, Jenkins and SDKMAN are not the same beasts, but they share some common
> ground: ideas from one may need to be adjusted.
>
> IIUC, discovery of available Maven versions could work on SDKMAN exactly
> like
> Jenkins
> Then there is the choice on default: for Maven, we publish the recommended
> version [1], and it is done with "currentStableVersion" property in maven-
> site's pom [2]
> Then extraction of this piece of information would be automatable also (and
> AFAIK, Jenkins does not take this "default" info into account currently)
>
> WDYT?
>
> Regards,
>
> Hervé
>
>
> [1] http://maven.apache.org/download.cgi
>
> [2]
>
> https://svn.apache.org/viewvc/maven/site/trunk/pom.xml?revision=HEAD&view=markup
>
> Le lundi 7 décembre 2015 09:01:43 Marco Vermeulen a écrit :
> > Most of the big projects want to do this. It puts them in control of
> > releasing and announcing their artifacts. FWIW, this is the model that
> > Gradle, Groovy, Grails, Ceylon and many others are following.
> >
> > Also, comparing sdkman to Jenkins is like comparing apples to oranges.
> >
> > Cheers,
> > Marco.
> >
> > On Mon, 7 Dec 2015 at 08:57, domi <domi@fortysix.ch> wrote:
> > > FWIW: I would try to free projects from having to do this - e.g. SDKMAN
> > > could crawl for new versions like Jenkins and Hudson are doing it [1].
> > > This way you don’t rely on anyone doing this and you get all versions
> > > integrated for free.
> > > /Domi
> > >
> > > [1]
> https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer
> > >
> > > > On 07 Dec 2015, at 08:23, Marco Vermeulen <vermeulen.mp@gmail.com>
> > >
> > > wrote:
> > > > Hi all,
> > > >
> > > > Do you have any feedback on the above?
> > > >
> > > > Regards,
> > > > Marco.
> > > > On Sun, 29 Nov 2015 at 22:01, Marco Vermeulen <
> vermeulen.mp@gmail.com>
> > > >
> > > > wrote:
> > > >> Hi Hervé,
> > > >>
> > > >> You needn't worry about Maven integration into sdkman, as it's
> built in
> > >
> > > a
> > >
> > > >> completely SDK agnostic way. Adding a new install candidate (like
> > > >> Maven)
> > > >> was a single row in our database. All subsequent interactions for
> you
> > > >> (like releasing new versions) happen through the Vendor API.
> > > >>
> > > >> In total, you would need to make 3 API calls to our Vendor API:
> > > >> 1) Release your new version on the sdkman platform
> > > >> 2) Set the new version as the default/stable version
> > > >> 3) Announce the release on the sdkman platform (and hence our
> twitter
> > >
> > > feed)
> > >
> > > >> In order to make these calls, you will need a key/token pair that
I
> > > >> will
> > > >> issue the person who agrees to taking this on. I will send the
> > > >> key/token
> > > >> pair in a pgp encrypted email, preferably using a service such as
> > > >> keybase.io
> > > >>
> > > >> As mentioned before, we have a maven plugin that performs all these
> api
> > > >> calls on your behalf, making it easy to tie into your release build:
> > > >> https://github.com/sdkman/sdkman-maven-plugin
> > > >>
> > > >> Hope this all makes sense now,
> > > >> Cheers,
> > > >> Marco.
> > > >>
> > > >>
> > > >> On Sun, 29 Nov 2015 at 15:21 Hervé BOUTEMY <herve.boutemy@free.fr>
> > >
> > > wrote:
> > > >>> Hi Marco,
> > > >>>
> > > >>> IIUC, you'll provide a key for the Maven PMC to announce new
> versions
> > >
> > > of
> > >
> > > >>> Maven
> > > >>> through Vendors API [1]
> > > >>>
> > > >>> I still don't see what is currently in the db for Maven
> > > >>>
> > > >>> And I don't see how Maven is integrated.
> > > >>>
> > > >>> Regards,
> > > >>>
> > > >>> Hervé
> > > >>>
> > > >>> [1] http://sdkman.io/vendors.html
> > > >>>
> > > >>> Le dimanche 29 novembre 2015 09:37:41 Marco Vermeulen a écrit
:
> > > >>>> Thanks for the reply Hervé.
> > > >>>>
> > > >>>> This is all explained in the links I posted. sdkman acts as
a
> broker,
> > > >>>> pointing to wherever the binary is hosted. Installing maven
is as
> > > >>>
> > > >>> simple as
> > > >>>
> > > >>>> entering 'sdk install maven' for latest stable, or 'sdk install
> maven
> > > >>>> x.y.z' for a particular version. This will do a curl to our
> central
> > > >>>
> > > >>> server
> > > >>>
> > > >>>> which will do a redirect to your hosted binary.
> > > >>>>
> > > >>>> Of course, sdkman is backed by a db that needs to be populated,
> > > >>>
> > > >>> preferably
> > > >>>
> > > >>>> by the owner of the sdk. In the interim I've added the latest
> > > >>>> versions
> > > >>>> myself, but it would be great if this is driven by the maven
team
> > > >>>> themselves.
> > > >>>>
> > > >>>> Hope this clarifies things a bit more.
> > > >>>>
> > > >>>> On Sun, 29 Nov 2015 at 00:56, Hervé BOUTEMY <
> herve.boutemy@free.fr>
> > > >>>
> > > >>> wrote:
> > > >>>>> IIUC, Maven is now supported by sdkman
> > > >>>>> But I still don't see how/where
> > > >>>>>
> > > >>>>> Where is the Maven support for SDKMAN hosted, that we
could
> > > >>>
> > > >>> contribute to?
> > > >>>
> > > >>>>> Regards,
> > > >>>>>
> > > >>>>> Hervé
> > > >>>>>
> > > >>>>> Notice: old issue about this is
> > > >>>>> https://issues.apache.org/jira/browse/MNG-5749
> > > >>>>>
> > > >>>>> Le vendredi 27 novembre 2015 08:07:33 Marco Vermeulen
a écrit :
> > > >>>>>> Hi all,
> > > >>>>>>
> > > >>>>>> I originally sent this directly to jvanzyl, but he
recommended I
> > > >>>
> > > >>> post
> > > >>>
> > > >>>>> this
> > > >>>>>
> > > >>>>>> to the dev forum.
> > > >>>>>>
> > > >>>>>> A word of introduction, I am Marco Vermeulen, the
project lead
> of
> > > >>>>>> SDKMAN,
> > > >>>>>> the Software Development Kit manager (formerly GVM).
We are
> > > >>>
> > > >>> responsible
> > > >>>
> > > >>>>> for
> > > >>>>>
> > > >>>>>> providing a free service that helps in distribution
of SDKs, and
> > > >>>
> > > >>> have
> > > >>>
> > > >>>>>> recently had several requests for Maven as install
candidate
> coming
> > > >>>>>
> > > >>>>> through.
> > > >>>>>
> > > >>>>>> I recently added Maven to SDKMAN, but wanted to know
if the
> Maven
> > > >>>
> > > >>> team
> > > >>>
> > > >>>>>> would be willing to push their own releases to our
platform.
> > > >>>>>>
> > > >>>>>> A little more information about SDKMAN can be found
at
> > > >>>
> > > >>> http://sdkman.io
> > > >>>
> > > >>>>> and
> > > >>>>>
> > > >>>>>> on our github page at https://github.com/sdkman/sdkman-cli.
> > > >>>>>>
> > > >>>>>> We expose a vendor API that can be called, more details
of that
> > > >>>
> > > >>> under
> > > >>>
> > > >>>>>> the
> > > >>>>>> Vendors section of our site. Of course we have a maven
plugin to
> > > >>>
> > > >>> make
> > > >>>
> > > >>>>> this
> > > >>>>>
> > > >>>>>> super easy and a part of your build pipeline.
> > > >>>>>>
> > > >>>>>> Please let me know your thoughts and if this sounds
feasible.
> > > >>>>>>
> > > >>>>>> Cheers!
> > > >>>>>>
> > > >>>>>> Marco.
> > > >>>>>
> > > >>>>>
> --------------------------------------------------------------------
> > > >>>>> -
> > > >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> > > >>>
> > > >>>
> ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > >>> For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message