maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aldrin Leal <ald...@leal.eng.br>
Subject Re: Publish Maven releases on SDKMAN!
Date Sun, 16 Apr 2017 09:51:34 GMT
just fyi: github releases has an atom feed.

https://github.com/apache/maven/releases.atom

--
-- Aldrin Leal, <aldrin@leal.eng.br> / http://about.me/aldrinleal

On Sun, Apr 16, 2017 at 4:49 AM, Marco Vermeulen <vermeulen.mp@gmail.com>
wrote:

> Hi Heinz,
>
> On Sun, 16 Apr 2017 at 08:41 Karl Heinz Marbaise <khmarbaise@gmx.de>
> 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-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