Re: Maven Docker Images

2017-10-21 Thread Manfred Moser
Following up on that remark and my earlier remark that we should NOT make this official .. here are my remarks: - so far the only binaries we assemble and call official are the tar.gz and zip archives (and even that is a gray line since official there are only sources from Apache) - we do NOT s

Re: [VOTE] Release Apache Maven 3.5.2

2017-10-21 Thread Dan Tran
ouch false alarm, I forgot to configure the artifactory mirror Sorry about the noise -D On Sat, Oct 21, 2017 at 10:10 AM, Dan Tran wrote: > I am not able getting mvn 3.5.2 to download an internal snapshot > dependency from comp's central artifactory > > here is the error > > Caused by: org.ec

Re: [VOTE] Release Apache Maven 3.5.2

2017-10-21 Thread Dan Tran
I am not able getting mvn 3.5.2 to download an internal snapshot dependency from comp's central artifactory here is the error Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact com.oracle.linux.x86_64:jre:rpm:1.8.0_151-SNAPSHOT at org.eclipse.aethe

Re: Maven Docker Images

2017-10-21 Thread Carlos Sanchez
On Sat, Oct 21, 2017 at 3:56 PM, Hervé BOUTEMY wrote: > notice that we vote on source tarballs, not really on binary artifacts > > I see the git source changes, both in Dockerfiles and in official-images > library/ > maven. > But I don't see when/how images are built > > can you explain, please?

Re: Maven Docker Images

2017-10-21 Thread Hervé BOUTEMY
notice that we vote on source tarballs, not really on binary artifacts I see the git source changes, both in Dockerfiles and in official-images library/ maven. But I don't see when/how images are built can you explain, please? Regards, Hervé Le samedi 21 octobre 2017, 10:59:45 CEST Carlos San

Re: Maven Docker Images

2017-10-21 Thread Hervé BOUTEMY
Le samedi 21 octobre 2017, 12:32:54 CEST Robert Scholte a écrit : > > One thing I see is that we can automate a check that the current > > official-image > > is our currently recommended Maven version: it's just about adding a new > > check > > to dist-tool-plugin that will be checked every day by

Re: moving GitHub issue notifications to issues@maven.a.o

2017-10-21 Thread Uwe Barthel
+1 (non binding) -- bart...@x-reizend.de > On 21. Oct 2017, at 12:22, Hervé BOUTEMY wrote: > > Currently, comments are sent to dev@maven.a.o > > For our classical official Jira issue tracker, notifications are sent to > issues@maven.a.o > > If nobody objects (72h as usual), I'll ask infra

Re: moving GitHub issue notifications to issues@maven.a.o

2017-10-21 Thread Olivier Lamy
+1 On 21 October 2017 at 21:23, Robert Scholte wrote: > +1 > > > On Sat, 21 Oct 2017 12:22:47 +0200, Hervé BOUTEMY > wrote: > > Currently, comments are sent to dev@maven.a.o >> >> For our classical official Jira issue tracker, notifications are sent to >> issues@maven.a.o >> >> If nobody object

Re: Maven Docker Images

2017-10-21 Thread Carlos Sanchez
BTW there are possibly more than one image build for each maven version. For a variety of reasons, like security issues in OS or to upgrade JDK or because docker rebuilds it, so it is not feasible to vote each of them. On Sat, Oct 21, 2017, 12:33 Robert Scholte wrote: > On Sat, 21 Oct 2017 12:19

Re: Maven Docker Images

2017-10-21 Thread Robert Scholte
On Sat, 21 Oct 2017 12:19:46 +0200, Hervé BOUTEMY wrote: Le samedi 21 octobre 2017, 08:16:35 CEST Stephen Connolly a écrit : On Sat 21 Oct 2017 at 08:45, Hervé BOUTEMY wrote: > ok, let's switch directly to the Docker case > > I'm not a Docker expert, then I'm discovering things that my be

Re: moving GitHub issue notifications to issues@maven.a.o

2017-10-21 Thread Robert Scholte
+1 On Sat, 21 Oct 2017 12:22:47 +0200, Hervé BOUTEMY wrote: Currently, comments are sent to dev@maven.a.o For our classical official Jira issue tracker, notifications are sent to issues@maven.a.o If nobody objects (72h as usual), I'll ask infra to switch GitHub issue notifications to isse

moving GitHub issue notifications to issues@maven.a.o

2017-10-21 Thread Hervé BOUTEMY
Currently, comments are sent to dev@maven.a.o For our classical official Jira issue tracker, notifications are sent to issues@maven.a.o If nobody objects (72h as usual), I'll ask infra to switch GitHub issue notifications to isseus@maven.a.o Regards, Hervé ---

Re: Maven Docker Images

2017-10-21 Thread Hervé BOUTEMY
Le samedi 21 octobre 2017, 08:16:35 CEST Stephen Connolly a écrit : > On Sat 21 Oct 2017 at 08:45, Hervé BOUTEMY wrote: > > ok, let's switch directly to the Docker case > > > > I'm not a Docker expert, then I'm discovering things that my be obvious to > > others > > > > IIUC Docker has an "offic

Re: Maven Docker Images

2017-10-21 Thread Stephen Connolly
On Sat 21 Oct 2017 at 08:45, Hervé BOUTEMY wrote: > ok, let's switch directly to the Docker case > > I'm not a Docker expert, then I'm discovering things that my be obvious to > others > > IIUC Docker has an "officiel images" project [1] where Carlos provided a > Maven > image [2]: then this imag

Re: Maven Docker Images

2017-10-21 Thread Hervé BOUTEMY
ok, let's switch directly to the Docker case I'm not a Docker expert, then I'm discovering things that my be obvious to others IIUC Docker has an "officiel images" project [1] where Carlos provided a Maven image [2]: then this image is known as "the official Maven Docker image" Carlos is an ind