>From my perspective it is just like sdkman including the conclusion. We have >other tasks at our hands, maintaining a docker images is not something we >should bother with. However needs one can easily create one and there will be >thousands of variations different users want.
Let them create it on their own. Manfred Hervé BOUTEMY wrote on 2017-10-20 18:46: > true, from a general perspective, it's like sdkman > > we need to discuss then decide if we want to maintain Maven Docker > integration > (contrary to our current decision to not maintain Maven sdkman integration > but > let sdkman community do it) > > can we think about a general solution? perhaps not really a solution, but a > decision process, yes > > to me, on each tool integration, there are key decision drivers: > - importance of the tool on the market > - interest of Maven devs to actually do integration maintenance > - complexity of integration, technical prerequisites (with IDEs, for example, > a dedicated independant project like m2e is necessary) > - time factor: things evolve over time (e.g. 2 years ago, Docker was not what > it is nowadays) > > any other key driver to document? > > once done, we'll discuss more precisely about the Docker integration case > > and probably finish with a vote :) > > Regards, > > Hervé > > Le vendredi 20 octobre 2017, 11:30:49 CEST Robert Scholte a écrit : >> Isn't this actually the same case as sdkman[1]? >> Just wondering if we need to think about a general solution instead of >> pulling everything into our project when possible. >> >> thanks, >> Robert >> >> [1] http://markmail.org/message/oofvszmf56tbr7et >> >> On Thu, 19 Oct 2017 19:30:57 +0200, Hervé BOUTEMY <herve.bout...@free.fr> >> >> wrote: >> > great idea >> > >> > ok, we need a git repo at ASF >> > >> > what else? >> > Is there some sort of release process? some sort of source to release? >> > >> > Regards, >> > >> > Hervé >> > >> > Le jeudi 19 octobre 2017, 13:47:45 CEST Mike Drob a écrit : >> >> Thanks for the pointer, Carlos! I had searched the archives, but maybe I >> >> didn't go back far enough. >> >> >> >> I think moving these Dockerfiles into an ASF repo would be great for >> >> their >> >> maintainability. >> >> >> >> Thanks, >> >> >> >> Mike >> >> >> >> On 2017-10-19 03:50, Carlos Sanchez <c...@apache.org> wrote: >> >> > Arnaud is correct, I sent an email to users@ back on Fri, Nov 7, >> >> >> >> 2014,> >> >> >> >> > 00:23 when I created the image> >> >> > >> >> > >> >> > On Thu, Oct 19, 2017, 11:12 Arnaud H�ritier <ah...@gmail.com> wrote:> >> >> > >> >> > > These images are kindly managed by a PMC member of our project >> >> >> >> (Carlos) >> >> >> >> but> >> >> >> >> > > yes they aren't managed directly by the project> >> >> > > >> >> > > We can easily see with him to improve this IMO.> >> >> > > >> >> > > When he started that (several years ago) Docker wasn't what it is >> >> >> >> nowadays.> >> >> >> >> > > With docker being mainstream I agree that we can reconsider this.> >> >> > > >> >> > > The docker image build/distribution could perhaps be part of our >> >> >> >> release> >> >> >> >> > > process.> >> >> > > >> >> > > WDYT Carlos ?> >> >> > > >> >> > > On Thu, Oct 19, 2017 at 4:16 AM, Mike Drob <md...@apache.org> >> >> >> >> wrote:> >> >> >> >> > > > I guess the natural follow-on question is whether the Maven >> >> >> >> community> >> >> >> >> > > > would consider publishing an official set of images? Or >> >> >> >> alternatively> >> >> >> >> > > > whether they should send a takedown notice to protect their brand >> >> >> >> and> >> >> >> >> > > > trademarks...> >> >> > > > >> >> > > > On 2017-10-18 18:36, "Manfred Moser" <ma...@simpligility.com> >> >> >> >> wrote:> >> >> >> >> > > > > No. As you can see from the github URL this is NOT an apache >> >> >> >> URL.> >> >> >> >> > > > > https://github.com/carlossg/docker-maven> >> >> > > > > >> >> > > > > >> >> > > > > Mike Drob wrote on 2017-10-18 16:32:> >> >> > > > > >> >> > > > > > Hello,> >> >> > > > > > >> >> > > > > > Are the images at https://hub.docker.com/r/_/maven/ >> >> >> >> considered to >> >> >> >> be> >> >> >> >> > > > official> >> >> > > > >> >> > > > > > maven docker images and blessed/published by the PMC?> >> >> > > > > > >> >> > > > > > Thanks,> >> >> > > > > > Mike> >> >> >> >> ---------------------------------------------------------------------> >> >> >> >> > > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org> >> >> > > > > > For additional commands, e-mail: users-h...@maven.apache.org> >> >> >> >> ---------------------------------------------------------------------> >> >> >> >> > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org> >> >> > > > > For additional commands, e-mail: users-h...@maven.apache.org> >> >> >> >> ---------------------------------------------------------------------> >> >> >> >> > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org> >> >> > > > For additional commands, e-mail: users-h...@maven.apache.org> >> >> > > >> >> > > --> >> >> > > -----> >> >> > > Arnaud H�ritier> >> >> > > http://aheritier.net> >> >> > > Mail/GTalk: aheritier AT gmail DOT com> >> >> > > Twitter/Skype : aheritier> >> > >> > --------------------------------------------------------------------- >> > 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 > > > > --------------------------------------------------------------------- > 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
