Re: [VOTE] Release Maven SCM version 1.11.1

+1 On Wed, 12 Sep 2018 at 07:36, Michael Osipov wrote: > Hi, > > We solved 31 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12343394 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2

Re: Question: EoL for Maven 3.0.5

+1 On Wed, 12 Sep 2018 at 18:00, Tibor Digana wrote: > Hi all, > > I would like to have Maven 3.1.1 instead in our Jenkins and env script of > Groovy on GitBox. > What is your opinion and needs? > > Tibor > > On Sun, Aug 19, 2018 at 11:24 AM Karl Heinz Marbaise > wrote: > > > Hi Robert, > > > >

[ANN] Apache Maven Shade Plugin Version 3.2.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Shade Plugin Version 3.2.0 https://maven.apache.org/plugins/maven-shade-plugin/ Important Note since 3.2.0: * Maven 3.X only * If you like to use minimizeJar you have to use JDK8+ otherwise you can keep running w

Re: [VOTE] Release Maven SCM version 1.11.1

Am 2018-09-11 um 23:36 schrieb Michael Osipov: Hi, We solved 31 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828&version=12343394 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SCM%20AND%20resolutio

[RESULT] [VOTE] Release Apache Maven Shad Plugin version 3.2.0

Hi, The vote has passed with the following result: +1 : Hervé Boutemy, Olivier Lamy, Tbor Digana, Karl Heinz Marbaise PMC quorum: reached. I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise -

Re: Our builds crashed on Jenkins system due to "Failed to collect dependencies"

no need to send it twice :) (it works from your gmail account) It's a very common error with Fastly see https://docs.fastly.com/guides/debugging/common-503-errors. And I think (not really sure of that) Sonatype is using fastly for central repo (https://www.fastly.com/customers/sonatype) so maybe it

Re: Our builds crashed on Jenkins system due to "Failed to collect dependencies"

(sent from my gmail account) ok, and how is the error code related to the message "Maximum threads for service reached"? Thx. Cheers Tibor On Wed, Sep 12, 2018 at 12:16 PM Olivier Lamy wrote: > On Wed, 12 Sep 2018 at 17:58, Tibor Digana wrote: > > > Hi all, > > > > Last time the build failed q

Re: Our builds crashed on Jenkins system due to "Failed to collect dependencies"

ok, and how is the error code related to the message "Maximum threads for service reached"? On Wed, Sep 12, 2018 at 12:16 PM Olivier Lamy wrote: > On Wed, 12 Sep 2018 at 17:58, Tibor Digana wrote: > > > Hi all, > > > > Last time the build failed quite often on connection problems with Maven > >

Re: Our builds crashed on Jenkins system due to "Failed to collect dependencies"

On Wed, 12 Sep 2018 at 17:58, Tibor Digana wrote: > Hi all, > > Last time the build failed quite often on connection problems with Maven > Central. > Sometimes the problem is connection timeout and sometimes it is HTTP 503. > Although in all cases I see "Maximum threads for service reached". > >

Re: Question: EoL for Maven 3.0.5

Hi all, I would like to have Maven 3.1.1 instead in our Jenkins and env script of Groovy on GitBox. What is your opinion and needs? Tibor On Sun, Aug 19, 2018 at 11:24 AM Karl Heinz Marbaise wrote: > Hi Robert, > > On 17/08/18 12:07, Robert Scholte wrote: > > Hi Karl Heinz, > > > > Maven 3.0.5

Our builds crashed on Jenkins system due to "Failed to collect dependencies"

Hi all, Last time the build failed quite often on connection problems with Maven Central. Sometimes the problem is connection timeout and sometimes it is HTTP 503. Although in all cases I see "Maximum threads for service reached". Does it mean that any thread pool in Wagon is limited or it is OS