Looks like yet another package manager, and just as most upstream projects don't provide the packages/build for every linux distro and package manager system under the sun, this project looks no different.
The sdkman community should help provide the maven releases on it, and not the maven community (they can however overlap). Regards On Sun, Apr 16, 2017 at 1:33 AM, Marco Vermeulen <[email protected]> wrote: > 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 <[email protected]> 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 >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
