Re: Publish Maven releases on SDKMAN!
Hi Maven folks, I really haven't come here to start a flame war or to give justification about why/how I built SDKMAN. Even less, justifying why I gave it such a "silly" name. I have come here with friendly intent to help your community publish their own releases on SDKMAN. I've come back since I was urged to do so [1] recently on Twitter by the @ASFMavenProject account. Publishing is as simple as a small API call which can be handled by anyone wishing to take up this responsibility in your community. I won't be defending myself or arguing with anyone on this forum going forward. I'm simply asking you for help. Plain and simple. I won't be changing the way SDKMAN works, since it already works well and is very reliable. All our vendors love it, and are very happy to integrate with us. In the process we all win: vendors are given control of their own releases and get another channel to distribute their software free of charge, and users have a convenient easy-to-use way to install their favourite software. I get to stand in the middle and watch it all happen asking nothing in return. I like contributing my free time to make developers happy and easing their installation pains. This is what I do to make our open source world a better place. If anyone in the community wants to step up and help with this process, feel free to contact me and I would be more than happy to get you set up. I would issue some API credentials and this would empower you to do a simple REST call to make Maven available to all our users across all platforms. Feel free to send me a mail at ma...@sdkman.io Many thanks! Marco. [1] https://twitter.com/ASFMavenProject/status/851132246669103108 On Sun, 16 Apr 2017 at 10:52 Aldrin Leal wrote: > just fyi: github releases has an atom feed. > > https://github.com/apache/maven/releases.atom > > -- > -- Aldrin Leal, / http://about.me/aldrinleal > > On Sun, Apr 16, 2017 at 4:49 AM, Marco Vermeulen > wrote: > > > Hi Heinz, > > > > On Sun, 16 Apr 2017 at 08:41 Karl Heinz Marbaise > > wrote: > > > > > Hi, > > > > > > On 16/04/17 00:56, Marco Vermeulen wrote: > > > > Hi Maven folks, > > > > > > > > Some time ago I asked the Maven dev community whether they would be > > > willing > > > > to publish their releases on SDKMAN! [1] using our Vendor API [2]. > > > > Unfortunately, my request was met with scepticism and ultimately > > resulted > > > > in no action taken. > > > > > > What happended out of the idea to scan automatically[1] for new > versions > > > and insert the data automatically via a crawler which can for example > > > scan maven central[2] where all releases of Maven will be distributed > > > (also there is a REST API on Maven Central)...or the distirbution > > pages... > > > > > > > > The idea to scan/crawl is not feasible for me as crawlers are brittle and > > time consuming to maintain. I provide SDKMAN in my spare time to help > > others, so don't want to spend my time maintaining something like this. > > Moreover, why write a piece of infrastructure when a simple API call from > > your side would do the trick? It would take almost no effort. > > > > > > > > > > [1]: https://www.mail-archive.com/dev@maven.apache.org/msg108018.html > > > [2]: > > > > > > http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org. > > apache.maven%22%20AND%20a%3A%22apache-maven%22 > > > > > > > > > > > > > > I would like to appeal to the Maven dev community again to take on > the > > > > responsibility of managing their own releases on our platform. > > > > > > Hm...maybe I misunderstand here a thing but which responsibily does the > > > Maven dev community has on your platform ? > > > > > > From my personell point view: none > > > > > > > The maven community has no responsibility, I am asking your community for > > help. I'm asking you in a friendly manner to take on the responsibility > of > > publishing, you misunderstood my intent. > > > > > > > > > > > The process > > > > is very simple: It involves making a few REST calls to our API and > > > > instantaneously releases become available for all the SDKMAN! users > out > > > > there. > > > > > > This is the point which is the problem...or the "scepticism" you > > > mentioned... > > > > > > To be honest you seemed to be ignoring the suggestions for improvements > > > on your platform which coul
Re: Publish Maven releases on SDKMAN!
Hi Heinz, On Sun, 16 Apr 2017 at 08:41 Karl Heinz Marbaise wrote: > Hi, > > On 16/04/17 00:56, Marco Vermeulen wrote: > > Hi Maven folks, > > > > Some time ago I asked the Maven dev community whether they would be > willing > > to publish their releases on SDKMAN! [1] using our Vendor API [2]. > > Unfortunately, my request was met with scepticism and ultimately resulted > > in no action taken. > > What happended out of the idea to scan automatically[1] for new versions > and insert the data automatically via a crawler which can for example > scan maven central[2] where all releases of Maven will be distributed > (also there is a REST API on Maven Central)...or the distirbution pages... > > The idea to scan/crawl is not feasible for me as crawlers are brittle and time consuming to maintain. I provide SDKMAN in my spare time to help others, so don't want to spend my time maintaining something like this. Moreover, why write a piece of infrastructure when a simple API call from your side would do the trick? It would take almost no effort. > > [1]: https://www.mail-archive.com/dev@maven.apache.org/msg108018.html > [2]: > > http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22apache-maven%22 > > > > > > I would like to appeal to the Maven dev community again to take on the > > responsibility of managing their own releases on our platform. > > Hm...maybe I misunderstand here a thing but which responsibily does the > Maven dev community has on your platform ? > > From my personell point view: none > The maven community has no responsibility, I am asking your community for help. I'm asking you in a friendly manner to take on the responsibility of publishing, you misunderstood my intent. > > > The process > > is very simple: It involves making a few REST calls to our API and > > instantaneously releases become available for all the SDKMAN! users out > > there. > > This is the point which is the problem...or the "scepticism" you > mentioned... > > To be honest you seemed to be ignoring the suggestions for improvements > on your platform which could make it easier to integrate parts on your > platform...not only for us also for many other tools...which would > improve the accepting for the support of your platform... > All the others communities out there were more than happy to do the API call. This community being the first out of all the others to show any resistance. Empowering SDK vendors by exposing an API seems by far more preferred among our vendors as it puts them in control of their own releases. Releases become available fast and reliably, and they have full control over this. > > In earlier days you have declined[1] to support maven at all now you > have changed your mind which of course is fine... > Yes, I changed my mind because I was urged [1] to do so on twitter by your very own twitter account. [1] https://twitter.com/ASFMavenProject/status/851132246669103108 > [3]: https://issues.apache.org/jira/browse/MNG-5749 > > > > > Many other teams are already doing this, including Gradle, Kotlin, > Groovy, > > Ceylon and Spring Boot to name a few. It would be great to have you guys > on > > board too. > > > > I currently perform these releases for Maven manually, which > unfortunately > > is not something I can sustain going forward. > > If the sdkman user community has already asked for support why don't you > solve the problem ? > > The problem has long been solved by us exposing an API. The problem here seems to be with an insular community who does not want to reach out to others to help. In this case, by making a simple API call at release time. > In three ways. Removing the manuall work for yourself, the acceptance of > your platform to support more tools and finally fulfill the need of your > user community...(Which I think is the most important part here). > > In particular if it could be done by using a curl call on maven central > or a little bit more if you like to scan the > http://maven.apache.org/docs/history.html page (jsoup is very easy) from > your site... > > In a nutshell I would say why not implementing a scan service yourself > which takes some time, but I got the impression that writing all these > mails/tickets etc. and discussions takes more time than implementing > such a service... > In a nutshell, from a software engineering perspective a push (API) is always preferred to a pull (crawler). I have enabled push on our platform and all the other software providers have loved it. Subsequently none have hesitated to adopted it. I won't be implementing an inferior pull model anytime soon, especially as this problem has already been solved very elegantly with an easy push. > > Kind regards > Karl Heinz Marbaise > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Publish Maven releases on SDKMAN!
Paul, I really am not trying to sell anything. I'm trying to help your community. You will get no *arguments* in favour or against from me. My users keep asking for Maven on SDKMAN, and I sincerely wish to give them what they ask for. Whether the community is willing to lend a hand is entirely up to the *committers* of this project. On Sun, 16 Apr 2017 at 00:12 Paul Hammant wrote: > Marco, > > You could sell your idea better, I think. You have "Most of the big > projects want to do this" as one of the stronger arguments in favor, which > isn't enough. For 20 years, Lean/Agilistas have focussed on "what is the > problem you're trying to solve?". And that is the question, I personally* > would want to make to you. > > * I'm an interloper to this list, not a committer. > > Maven experts really do one setup thing: "brew install maven" (or equiv). > > Then they clone repos that purport to be example applications for the think > they want (SpringBoot, Grails). Then they mvn install that and the bits of > the SDK they need come down to their local cache. It has been four years > since I last acquired a new JVM technology any other way. > > - Paul >
Publish Maven releases on SDKMAN!
Hi Maven folks, Some time ago I asked the Maven dev community whether they would be willing to publish their releases on SDKMAN! [1] using our Vendor API [2]. Unfortunately, my request was met with scepticism and ultimately resulted in no action taken. I would like to appeal to the Maven dev community again to take on the responsibility of managing their own releases on our platform. The process is very simple: It involves making a few REST calls to our API and instantaneously releases become available for all the SDKMAN! users out there. Many other teams are already doing this, including Gradle, Kotlin, Groovy, Ceylon and Spring Boot to name a few. It would be great to have you guys on board too. I currently perform these releases for Maven manually, which unfortunately is not something I can sustain going forward. Please let me know if someone is willing to step up to this and feel free to contact me directly at ma...@sdkman.io Cheers! Marco. [1] http://sdkman.io [2] http://sdkman.io/vendors.html
Re: Inclusion of Maven on SDKMAN
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 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 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 > > > > > > wrote: > > > > Hi all, > > > > > > > > Do you have any feedback on the above? > > > > > > > > Regards, > > > > Marco. > > > > On Sun, 29 Nov 2015 at 22:01, Marco Vermeulen < > vermeulen...@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 buil
Re: Inclusion of Maven on SDKMAN
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 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 > wrote: > > > > Hi all, > > > > Do you have any feedback on the above? > > > > Regards, > > Marco. > > On Sun, 29 Nov 2015 at 22:01, Marco Vermeulen > > 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 > 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 > >>> 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 thi
Re: Inclusion of Maven on SDKMAN
Hi all, Do you have any feedback on the above? Regards, Marco. On Sun, 29 Nov 2015 at 22:01, Marco Vermeulen 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 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 >> 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-unsubscr...@maven.apache.org >> > > For additional commands, e-mail: dev-h...@maven.apache.org >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >>
Re: Inclusion of Maven on SDKMAN
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 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 > 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-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Inclusion of Maven on SDKMAN
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 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-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Inclusion of Maven on SDKMAN
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.
