Re: Maven Docker Images

2017-10-20 Thread Manfred Moser 
>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 
>> 
>> 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  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  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 
>> >> 
>> >> 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" 
>> >> 
>> >> 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:

Re: [VOTE] Release Apache Maven 3.5.2

2017-10-20 Thread Mark Derricutt 
+1 looking good from here on my projects/releases.

-- 
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree

On Wed, Oct 18, 2017 at 11:50 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Hi,
>
> We solved 26 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12338964=Text=12316922
>
> There are 357 issues left in JIRA for Maven core:
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%
> 20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1373/
>
> The distributable binaries and sources can be found here:
> https://repository.apache.org/content/repositories/maven-
> 1373/org/apache/maven/apache-maven/3.5.2/
>
> Specifically the zip, tarball and source archives can be found here:
> https://repository.apache.org/content/repositories/maven-
> 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip
> https://repository.apache.org/content/repositories/maven-
> 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.tar.gz
> https://repository.apache.org/content/repositories/maven-
> 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip
> https://repository.apache.org/content/repositories/maven-
> 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.tar.gz
>
> Source release checksum(s):
> apache-maven-3.5.2-src.tar.gz sha1: 97d6d7b18485b7906dd7f313cdd411
> 91d16dde46
> apache-maven-3.5.2-src.zip: sha1: dc8caa5cdacb400943d2491a020f742a518e8f08
>
> Git tag:
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=
> 138edd61fd100ec658bfa2d307c43b76940a5d7d
>
> Staging site:
> https://maven.apache.org/components/ref/3-LATEST/
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> Thanks,
>
> Stephen.
>

Re: [VOTE] Release Apache Maven 3.5.2

2017-10-20 Thread Hervé BOUTEMY 
+1
tested on Linux and Windows 10 (with cmd, PowerShell, GitBash, Cygwin)

this time, color appears on Windows in every configuration I know of :)

verification of binary artifacts: I tried to compare binary artifacts built 
locally with artifacts in staging repo (using diffoscope)

Good news: using my own JDK 8 (which is not exactly the same as Stephen, and I 
suppose we don't have the same OS: OSX vs Linux), I got the same .class 
binaries
The only differences are the usual ones on generated content: I found 2 
notable new little differences in maven-core-3.5.2.jar:
1. META-INF/sisu/javax.inject.Named content ordering (not a surprise given 
same issue in META-INF/plexus/components.xml)
2. org/apache/maven/messages/build.properties:
  -buildNumber=NON-CANONICAL_2017-10-20T00:16:35+02:00_herve
  -timestamp=1508451395983
  +buildNumber=138edd61fd100ec658bfa2d307c43b76940a5d7d
  +timestamp=1508313493546

this second difference is important to me, since this is exactly one case 
where "reproducible build" objective is against another key Apache objective, 
which is to build from source tarball disconnected from scm and keep 
traceability inside the built artifact

but in general, this makes me think that by defining the major level of JDK 
used to build the reference binary artifacts (and improving the known issues), 
we can get binary verifiable artifacts
ie we can check that the artifacts are not modified by simply checking hash 
(instead of using diffoscope and manually analyzing the output)

Regards,

Hervé

Le mercredi 18 octobre 2017, 03:50:43 CEST Stephen Connolly a écrit :
> Hi,
> 
> We solved 26 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338964
> eName=Text=12316922
> 
> There are 357 issues left in JIRA for Maven core:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resol
> ution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20
> created%20ASC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1373/
> 
> The distributable binaries and sources can be found here:
> https://repository.apache.org/content/repositories/maven-1373/org/apache/mav
> en/apache-maven/3.5.2/
> 
> Specifically the zip, tarball and source archives can be found here:
> https://repository.apache.org/content/repositories/maven-1373/org/apache/mav
> en/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip
> https://repository.apache.org/content/repositories/maven-1373/org/apache/ma
> ven/apache-maven/3.5.2/apache-maven-3.5.2-bin.tar.gz
> https://repository.apache.org/content/repositories/maven-1373/org/apache/ma
> ven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip
> https://repository.apache.org/content/repositories/maven-1373/org/apache/ma
> ven/apache-maven/3.5.2/apache-maven-3.5.2-src.tar.gz
> 
> Source release checksum(s):
> apache-maven-3.5.2-src.tar.gz sha1: 97d6d7b18485b7906dd7f313cdd41191d16dde46
> apache-maven-3.5.2-src.zip: sha1: dc8caa5cdacb400943d2491a020f742a518e8f08
> 
> Git tag:
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=138edd61fd100
> ec658bfa2d307c43b76940a5d7d
> 
> Staging site:
> https://maven.apache.org/components/ref/3-LATEST/
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> Thanks,
> 
> Stephen.



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Docker Images

2017-10-20 Thread Hervé BOUTEMY 
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 
> 
> 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  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  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 
> >> 
> >> 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" 
> >> 
> >> 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

[GitHub] maven issue #109: Update Mockito to 2.x

2017-10-20 Thread hboutemy 
Github user hboutemy commented on the issue:

https://github.com/apache/maven/pull/109
  
great, thank you


---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 3.5.2

2017-10-20 Thread Petr Široký 
+1 (non-binding)

Tested with OracleJDK 1.8.0_144 on several large multi-module projects. No
issue found.

Petr

On Fri, Oct 20, 2017 at 9:46 PM Arnaud Héritier  wrote:

> +1 for me too
> Used it with no issue (but my usages are limited)
>
> On Fri, Oct 20, 2017 at 8:34 PM, Robert Scholte 
> wrote:
>
> > +1
> >
> >
> > On Wed, 18 Oct 2017 12:50:43 +0200, Stephen Connolly <
> > stephen.alan.conno...@gmail.com> wrote:
> >
> > Hi,
> >>
> >> We solved 26 issues:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?versi
> >> on=12338964=Text=12316922
> >>
> >> There are 357 issues left in JIRA for Maven core:
> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%
> >> 20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
> >> 20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >>
> >> Staging repo:
> >> https://repository.apache.org/content/repositories/maven-1373/
> >>
> >> The distributable binaries and sources can be found here:
> >> https://repository.apache.org/content/repositories/maven-137
> >> 3/org/apache/maven/apache-maven/3.5.2/
> >>
> >> Specifically the zip, tarball and source archives can be found here:
> >> https://repository.apache.org/content/repositories/maven-137
> >> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip
> >> https://repository.apache.org/content/repositories/maven-137
> >> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.tar.gz
> >> https://repository.apache.org/content/repositories/maven-137
> >> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip
> >> https://repository.apache.org/content/repositories/maven-137
> >> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.tar.gz
> >>
> >> Source release checksum(s):
> >> apache-maven-3.5.2-src.tar.gz sha1: 97d6d7b18485b7906dd7f313cdd411
> >> 91d16dde46
> >> apache-maven-3.5.2-src.zip: sha1: dc8caa5cdacb400943d2491a020f74
> >> 2a518e8f08
> >>
> >> Git tag:
> >> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit
> >> ;h=138edd61fd100ec658bfa2d307c43b76940a5d7d
> >>
> >> Staging site:
> >> https://maven.apache.org/components/ref/3-LATEST/
> >>
> >> Vote open for 72 hours.
> >>
> >> [ ] +1
> >> [ ] +0
> >> [ ] -1
> >>
> >> Thanks,
> >>
> >> Stephen.
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
>
> --
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>

Re: [VOTE] Release Apache Maven 3.5.2

2017-10-20 Thread Arnaud Héritier 
+1 for me too
Used it with no issue (but my usages are limited)

On Fri, Oct 20, 2017 at 8:34 PM, Robert Scholte 
wrote:

> +1
>
>
> On Wed, 18 Oct 2017 12:50:43 +0200, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> Hi,
>>
>> We solved 26 issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?versi
>> on=12338964=Text=12316922
>>
>> There are 357 issues left in JIRA for Maven core:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%
>> 20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
>> 20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-1373/
>>
>> The distributable binaries and sources can be found here:
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/
>>
>> Specifically the zip, tarball and source archives can be found here:
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.tar.gz
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.tar.gz
>>
>> Source release checksum(s):
>> apache-maven-3.5.2-src.tar.gz sha1: 97d6d7b18485b7906dd7f313cdd411
>> 91d16dde46
>> apache-maven-3.5.2-src.zip: sha1: dc8caa5cdacb400943d2491a020f74
>> 2a518e8f08
>>
>> Git tag:
>> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit
>> ;h=138edd61fd100ec658bfa2d307c43b76940a5d7d
>>
>> Staging site:
>> https://maven.apache.org/components/ref/3-LATEST/
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>> Thanks,
>>
>> Stephen.
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Re: [VOTE] Release Apache Maven 3.5.2

2017-10-20 Thread Robert Scholte 

+1

On Wed, 18 Oct 2017 12:50:43 +0200, Stephen Connolly  
 wrote:



Hi,

We solved 26 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338964=Text=12316922

There are 357 issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC

Staging repo:
https://repository.apache.org/content/repositories/maven-1373/

The distributable binaries and sources can be found here:
https://repository.apache.org/content/repositories/maven-1373/org/apache/maven/apache-maven/3.5.2/

Specifically the zip, tarball and source archives can be found here:
https://repository.apache.org/content/repositories/maven-1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip
https://repository.apache.org/content/repositories/maven-1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.tar.gz
https://repository.apache.org/content/repositories/maven-1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip
https://repository.apache.org/content/repositories/maven-1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.tar.gz

Source release checksum(s):
apache-maven-3.5.2-src.tar.gz sha1:  
97d6d7b18485b7906dd7f313cdd41191d16dde46
apache-maven-3.5.2-src.zip: sha1:  
dc8caa5cdacb400943d2491a020f742a518e8f08


Git tag:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=138edd61fd100ec658bfa2d307c43b76940a5d7d

Staging site:
https://maven.apache.org/components/ref/3-LATEST/

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Thanks,

Stephen.


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven plugins, Java 9, and split packages

2017-10-20 Thread Mark Raynsford 
On 2017-10-20T14:43:52 +0200
"Robert Scholte"  wrote:
>
> > This looks to be a case of split packages amongst all of the various
> > Maven artifacts. I'm adding dependency exclusions to try to work around
> > the issues, but I'm not confident that'll actually work.
> >
> > Are there efforts underway to clean this stuff up?  
> 
> No, Maven has its own modular system long before the Java Platform Modular  
> System (JPMS)...

OK, makes sense. I was seeing errors related to Class.byName in some of
the exceptions I was seeing, so I mistakenly assumed that there was
some degree of modularization underway that possibly wasn't quite
complete yet. I suspect the actual problems I'm seeing here are just
out-of-date dependencies.

> > The reason I'm modularizing the plugin is due to this:
> >
> >   "To build and run japicmp under Java 1.9, you must add the following  
> > module: java.xml.bind. This can be done for the maven plugin for example  
> > by:
> >
> > export MAVEN_OPTS="--add-modules java.xml.bind"  
> 
> IIUC this doesn't mean you have to introduce a module descriptor (i.e.  
> module-info.java ).
> 
> The reason is that this module is marked as deprecated and won't be  
> activated by the JDK/JRE by default. By adding this argument it is loaded  
> anyway.
> 
> What you should try to do instead is add the following dependency:
> 
>  javax.xml.bind
>  jaxb-api
>  2.3.0
> 

Noted, thanks! I'll be testing this out today.

-- 
Mark Raynsford | http://www.io7m.com



pgpm9GhabWg7Q.pgp
Description: OpenPGP digital signature

Re: Maven plugins, Java 9, and split packages

2017-10-20 Thread Robert Scholte 


This looks to be a case of split packages amongst all of the various
Maven artifacts. I'm adding dependency exclusions to try to work around
the issues, but I'm not confident that'll actually work.

Are there efforts underway to clean this stuff up?


No, Maven has its own modular system long before the Java Platform Modular  
System (JPMS).
Due to the evolution of Maven over the last decade there are indeed split  
packages, which was never an issue.
Cleaning up is simply not possible and not necessary, unless we make a  
monolith of it, which is actually the opposite of want you want to achieve  
with modularization.
Cleaning up would mean introducing new packages, which would effectively  
make all current maven-plugins useless.

For that reason I see no reason to make it JPMS-modular.



The reason I'm modularizing the plugin is due to this:

  "To build and run japicmp under Java 1.9, you must add the following  
module: java.xml.bind. This can be done for the maven plugin for example  
by:


export MAVEN_OPTS="--add-modules java.xml.bind"


IIUC this doesn't mean you have to introduce a module descriptor (i.e.  
module-info.java ).


The reason is that this module is marked as deprecated and won't be  
activated by the JDK/JRE by default. By adding this argument it is loaded  
anyway.


What you should try to do instead is add the following dependency:

javax.xml.bind
jaxb-api
2.3.0


thanks,
Robert



I'd rather not have to do this as I'm committed to having all of my
project builds run without needing extra Maven flags: "mvn clean install"
*must* just work on every system, no exceptions.

Am I undertaking a fool's errand trying to get this stuff to work  
cleanly?

If not, is there any documentation on modularizing existing plugins?

[0] https://github.com/siom79/japicmp/


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven 3.5.2

2017-10-20 Thread Stephen Connolly 
+1 from me, tested on a number of projects for the last couple of days...
not found any regressions from 3.5.0

On 18 October 2017 at 03:51, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Analyzer...
>
> stagingUrl: https://repository.apache.org/content/repositories/maven-1373
> groupId: org.apache.maven
> artifactId: apache-maven
> version: 3.5.2
>
> Source ZIP url exists.
> https://repository.apache.org/content/repositories/maven-
> 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip
>
> Source ZIP SHA1 url exists.
> https://repository.apache.org/content/repositories/maven-
> 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip.sha1
>
> Binary ZIP url exists.
> https://repository.apache.org/content/repositories/maven-
> 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip
>
> Binary ZIP SHA1 url exists.
> https://repository.apache.org/content/repositories/maven-
> 1373/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip.sha1
>
> Calculated SHA1 of source ZIP matches published SHA1 of source ZIP.
> dc8caa5cdacb400943d2491a020f742a518e8f08
>
> Calculated SHA1 of binary ZIP matches published SHA1 of binary ZIP.
> 23adadc90b7f79ad84bd14574581d0145611bfda
>
> Git revision of release as determined from maven-core-3.5.2.jar:org/
> apache/maven/messages/build.properties(buildNumber):
> 138edd61fd100ec658bfa2d307c43b76940a5d7d
>
> Files that are present in the source distribution but not in the source
> revision:
> DEPENDENCIES
>
>
> On 18 October 2017 at 03:50, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> Hi,
>>
>> We solved 26 issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?versi
>> on=12338964=Text=12316922
>>
>> There are 357 issues left in JIRA for Maven core:
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%
>> 20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%
>> 20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-1373/
>>
>> The distributable binaries and sources can be found here:
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/
>>
>> Specifically the zip, tarball and source archives can be found here:
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.zip
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-bin.tar.gz
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.zip
>> https://repository.apache.org/content/repositories/maven-137
>> 3/org/apache/maven/apache-maven/3.5.2/apache-maven-3.5.2-src.tar.gz
>>
>> Source release checksum(s):
>> apache-maven-3.5.2-src.tar.gz sha1: 97d6d7b18485b7906dd7f313cdd411
>> 91d16dde46
>> apache-maven-3.5.2-src.zip: sha1: dc8caa5cdacb400943d2491a020f74
>> 2a518e8f08
>>
>> Git tag:
>> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit
>> ;h=138edd61fd100ec658bfa2d307c43b76940a5d7d
>>
>> Staging site:
>> https://maven.apache.org/components/ref/3-LATEST/
>>
>> Vote open for 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>> Thanks,
>>
>> Stephen.
>>
>
>

Maven plugins, Java 9, and split packages

2017-10-20 Thread Mark Raynsford 
Hello.

I'm experimenting with modularizing an existing plugin (japicmp [0])
and am running into hundreds of errors of the form:

[ERROR] the unnamed module reads package org.apache.maven.plugin from both 
maven.plugin.api and maven.core
[ERROR] the unnamed module reads package org.apache.maven.artifact from both 
maven.artifact and maven.core
[ERROR] the unnamed module reads package org.apache.maven.artifact.resolver 
from both maven.artifact and maven.core
[ERROR] the unnamed module reads package 
org.apache.maven.artifact.resolver.filter from both maven.artifact and 
maven.core
[ERROR] the unnamed module reads package org.apache.maven.artifact.repository 
from both maven.artifact and maven.core
[ERROR] the unnamed module reads package 
org.apache.maven.artifact.repository.metadata from both maven.artifact and 
maven.core
[ERROR] the unnamed module reads package 
org.apache.maven.artifact.repository.layout from both maven.artifact and 
maven.core
[ERROR] the unnamed module reads package org.apache.maven.artifact.metadata 
from both maven.artifact and maven.core
[ERROR] the unnamed module reads package org.apache.maven.artifact.handler from 
both maven.artifact and maven.core
[ERROR] the unnamed module reads package 
org.apache.maven.artifact.handler.manager from both maven.artifact and 
maven.core
[ERROR] the unnamed module reads package org.apache.maven.artifact.factory from 
both maven.artifact and maven.core
[ERROR] module maven.plugin.annotations reads package org.apache.maven.plugin 
from both maven.plugin.api and maven.core
[ERROR] module maven.plugin.annotations reads package org.apache.maven.artifact 
from both maven.artifact and maven.core
[ERROR] module maven.plugin.annotations reads package 
org.apache.maven.artifact.resolver from both maven.artifact and maven.core
[ERROR] module maven.plugin.annotations reads package 
org.apache.maven.artifact.resolver.filter from both maven.artifact and 
maven.core
[ERROR] module maven.plugin.annotations reads package 
org.apache.maven.artifact.repository from both maven.artifact and maven.core
[ERROR] module maven.plugin.annotations reads package 
org.apache.maven.artifact.repository.metadata from both maven.artifact and 
maven.core
[ERROR] module maven.plugin.annotations reads package 
org.apache.maven.artifact.repository.layout from both maven.artifact and 
maven.core
[ERROR] module maven.plugin.annotations reads package 
org.apache.maven.artifact.metadata from both maven.artifact and maven.core
[ERROR] module maven.plugin.annotations reads package 
org.apache.maven.artifact.handler from both maven.artifact and maven.core
[ERROR] module maven.plugin.annotations reads package 
org.apache.maven.artifact.handler.manager from both maven.artifact and 
maven.core
[ERROR] module maven.plugin.annotations reads package 
org.apache.maven.artifact.factory from both maven.artifact and maven.core
[ERROR] module maven.plugin.api reads package org.apache.maven.plugin from both 
maven.plugin.api and maven.core
[ERROR] module maven.plugin.api reads package org.apache.maven.artifact from 
both maven.artifact and maven.core
[ERROR] module maven.plugin.api reads package 
org.apache.maven.artifact.resolver from both maven.artifact and maven.core
[ERROR] module maven.plugin.api reads package 
org.apache.maven.artifact.resolver.filter from both maven.artifact and 
maven.core
[ERROR] module maven.plugin.api reads package 
org.apache.maven.artifact.repository from both maven.artifact and maven.core
[ERROR] module maven.plugin.api reads package 
org.apache.maven.artifact.repository.metadata from both maven.artifact and 
maven.core
[ERROR] module maven.plugin.api reads package 
org.apache.maven.artifact.repository.layout from both maven.artifact and 
maven.core
[ERROR] module maven.plugin.api reads package 
org.apache.maven.artifact.metadata from both maven.artifact and maven.core
[ERROR] module maven.plugin.api reads package org.apache.maven.artifact.handler 
from both maven.artifact and maven.core
[ERROR] module maven.plugin.api reads package 
org.apache.maven.artifact.handler.manager from both maven.artifact and 
maven.core
[ERROR] module maven.plugin.api reads package org.apache.maven.artifact.factory 
from both maven.artifact and maven.core
[ERROR] module maven.artifact reads package org.apache.maven.plugin from both 
maven.plugin.api and maven.core
[ERROR] module maven.artifact reads package org.apache.maven.artifact from both 
maven.artifact and maven.core
[ERROR] module maven.artifact reads package org.apache.maven.artifact.resolver 
from both maven.artifact and maven.core
[ERROR] module maven.artifact reads package 
org.apache.maven.artifact.resolver.filter from both maven.artifact and 
maven.core
[ERROR] module maven.artifact reads package 
org.apache.maven.artifact.repository from both maven.artifact and maven.core
[ERROR] module maven.artifact reads package 
org.apache.maven.artifact.repository.metadata from both maven.artifact and 
maven.core
[ERROR] module

[GitHub] maven issue #109: Update Mockito to 2.x

2017-10-20 Thread slachiewicz 
Github user slachiewicz commented on the issue:

https://github.com/apache/maven/pull/109
  
ok, MNG-6196 with slf4j was merged to master - i'm clossing this issue. 
Mockito will be in diffrent pull.


---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven pull request #109: Update Mockito to 2.x

2017-10-20 Thread slachiewicz 
Github user slachiewicz closed the pull request at:

https://github.com/apache/maven/pull/109


---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Docker Images

2017-10-20 Thread Robert Scholte 

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   
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  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  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   
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"   
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

Re: Maven Docker Images

2017-10-20 Thread Carlos Sanchez 
Official docker images are not pushed to dockerhub. Docker builds them from
sources at GitHub
https://github.com/docker-library/official-images/blob/master/library/maven

On Fri, Oct 20, 2017, 08:20 Maxim Solodovnik  wrote:

> I would start with filing INFRA ticket :)
>
> On Fri, Oct 20, 2017 at 12:40 PM, Hervé BOUTEMY 
> wrote:
>
> > awesome: there is some common practice we should get into
> >
> > do you know if there some docs somewhere?
> > I suppose there are some credentials associated to publishing to
> Dockerhub
> >
> > Regards,
> >
> > Hervé
> >
> > Le vendredi 20 octobre 2017, 11:39:22 CEST Maxim Solodovnik a écrit :
> > > In this case dockerhub is preferable :)
> > >
> > > On Fri, Oct 20, 2017 at 11:07 AM, Bindul Bhowmik <
> > bindulbhow...@gmail.com>
> > >
> > > wrote:
> > > > Maxim,
> > > >
> > > > On Thu, Oct 19, 2017 at 7:54 PM, Maxim Solodovnik <
> > solomax...@gmail.com>
> > > >
> > > > wrote:
> > > > > Hello,
> > > > >
> > > > > here is the place for Apache docker images managed by infra and
> > Apache
> > > > > projects https://bintray.com/apache/ :)
> > > >
> > > > From what I have seen, while there are 4 projects with docker
> > > > repositories on bintray, there seem to be a lot more at dockerhub
> [1].
> > > > I did a quick search on INFRA JIRA and found that infra has set a few
> > > > projects up on dockerhub recently [2], for example INFRA-14756 [3]
> for
> > > > bookkeeper.
> > > >
> > > > Bindul
> > > >
> > > > [1] https://hub.docker.com/r/apache/
> > > > [2] https://issues.apache.org/jira/issues/?jql=component%20%
> > > > 3D%20Docker%20AND%20project%20%3D%20INFRA
> > > > [3] https://issues.apache.org/jira/browse/INFRA-14756
> > > >
> > > > > On Fri, Oct 20, 2017 at 12:30 AM, 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  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  >
> > > >
> > > > 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

Re: Maven Docker Images

2017-10-20 Thread Maxim Solodovnik 
I would start with filing INFRA ticket :)

On Fri, Oct 20, 2017 at 12:40 PM, Hervé BOUTEMY 
wrote:

> awesome: there is some common practice we should get into
>
> do you know if there some docs somewhere?
> I suppose there are some credentials associated to publishing to Dockerhub
>
> Regards,
>
> Hervé
>
> Le vendredi 20 octobre 2017, 11:39:22 CEST Maxim Solodovnik a écrit :
> > In this case dockerhub is preferable :)
> >
> > On Fri, Oct 20, 2017 at 11:07 AM, Bindul Bhowmik <
> bindulbhow...@gmail.com>
> >
> > wrote:
> > > Maxim,
> > >
> > > On Thu, Oct 19, 2017 at 7:54 PM, Maxim Solodovnik <
> solomax...@gmail.com>
> > >
> > > wrote:
> > > > Hello,
> > > >
> > > > here is the place for Apache docker images managed by infra and
> Apache
> > > > projects https://bintray.com/apache/ :)
> > >
> > > From what I have seen, while there are 4 projects with docker
> > > repositories on bintray, there seem to be a lot more at dockerhub [1].
> > > I did a quick search on INFRA JIRA and found that infra has set a few
> > > projects up on dockerhub recently [2], for example INFRA-14756 [3] for
> > > bookkeeper.
> > >
> > > Bindul
> > >
> > > [1] https://hub.docker.com/r/apache/
> > > [2] https://issues.apache.org/jira/issues/?jql=component%20%
> > > 3D%20Docker%20AND%20project%20%3D%20INFRA
> > > [3] https://issues.apache.org/jira/browse/INFRA-14756
> > >
> > > > On Fri, Oct 20, 2017 at 12:30 AM, 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  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 
> > >
> > > 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  >
> > > > >
> > > > > 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-unsubscribe@maven.
> apache.org
> > >
> > > > > > > > > > > For additional commands, e-mail:
> > >