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 <[email protected]> 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 <[email protected]>
> 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: [email protected]
> > > For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to