[jira] [Commented] (MINDEXER-81) Make ArtifactInfo extensible
[
https://issues.apache.org/jira/browse/MINDEXER-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949969#comment-15949969
]
Laird Nelson commented on MINDEXER-81:
--
I have a concrete use case that I'll elaborate here. I am a new user of Lucene
(no idea what I'm doing :-)) and of the Maven Indexer. Hopefully my
explanation below will give you insight into how a person new to this project
approaches it.
I'd like to write an {{IndexCreator}} that, in the abstract, adds fields to the
index that represent certain contents of {{META-INF/MANIFEST.MF}} files. I'd
like to let users search, for example, for artifacts containing
{{META-INF/MANIFEST.MF}} files with {{Fred}} in their {{Class-Path}} headers.
I see no way to simply write an {{IndexCreator}} (and no other code) to do
this. It seems that I would (with the current architecture) have to edit
{{ArtifactInfo}} to have some new instance variables to store this information.
It also looks like other {{IndexCreator}} implementations that work with
{{META-INF/MANIFEST.MF}} files, like the {{OsgiArtifactIndexCreator}}, do
exactly this: I note that {{ArtifactInfo}}, though it would seem to _want_ to
be a generic sort of class, has fields in it like
[{{bundleSymbolicName}}|https://github.com/apache/maven-indexer/blob/master/indexer-core/src/main/java/org/apache/maven/index/ArtifactInfo.java#L236],
suggesting that for every indexer an edit to {{ArtifactInfo}}'s source code is
necessary. This shouldn't be the case.
> Make ArtifactInfo extensible
>
>
> Key: MINDEXER-81
> URL: https://issues.apache.org/jira/browse/MINDEXER-81
> Project: Maven Indexer
> Issue Type: Improvement
>Reporter: Cservenak, Tamas
> Fix For: 6.0
>
>
> Make ArtifactInfo extensible, a followup of MINDEXER-32
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1342) Acknowledge normal exit of JVM and drain shared memory between processes
[
https://issues.apache.org/jira/browse/SUREFIRE-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949809#comment-15949809
]
Hudson commented on SUREFIRE-1342:
--
SUCCESS: Integrated in Jenkins build maven-surefire #1680 (See
[https://builds.apache.org/job/maven-surefire/1680/])
[SUREFIRE-1342] Acknowledge normal exit of JVM and drain shared memory
(tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git=commit=da7ff6aa25a72094705c24981afbf8294ac4b1dc])
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ThreadedStreamConsumer.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/lazytestprovider/TestProvidingInputStream.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/booter/CommandReader.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/booter/MasterProcessCommand.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/lazytestprovider/TestProvidingInputStreamTest.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/lazytestprovider/NotifiableTestStream.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/lazytestprovider/AbstractCommandStream.java
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/booterclient/MockNotifiableTestStream.java
* (edit)
surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/lazytestprovider/TestLessInputStream.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/booter/Shutdown.java
* (edit)
surefire-api/src/test/java/org/apache/maven/surefire/booter/MasterProcessCommandTest.java
* (edit)
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire141PluggableProvidersIT.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ForkClient.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/util/internal/DumpFileUtils.java
* (edit)
surefire-api/src/main/java/org/apache/maven/surefire/booter/Command.java
> Acknowledge normal exit of JVM and drain shared memory between processes
>
>
> Key: SUREFIRE-1342
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1342
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> Version {{2.19.1}} and the prior ones sent the event {{BYE}} and then the
> forked JVM exited.
> This caused the {{stdin}} buffer could not be read completely.
> The completion of JVM could not be marked in master process in Maven and
> therefore it was considered as a serious JVM error.
> Version {{2.19.2}} implemented acknowledgement of JVM exit by sending
> {{BYE_ACK}} command from master to the fork.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SUREFIRE-1342) Acknowledge normal exit of JVM and drain shared memory between processes
[
https://issues.apache.org/jira/browse/SUREFIRE-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1342:
---
Description:
Version {{2.19.1}} and the prior ones sent the event {{BYE}} and then the
forked JVM exited.
This caused the {{stdin}} buffer could not be read completely.
The completion of JVM could not be marked in master process in Maven and
therefore it was considered as a serious JVM error.
Version {{2.19.2}} implemented acknowledgement of JVM exit by sending
{{BYE_ACK}} command from master to the fork.
> Acknowledge normal exit of JVM and drain shared memory between processes
>
>
> Key: SUREFIRE-1342
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1342
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.19.1
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> Version {{2.19.1}} and the prior ones sent the event {{BYE}} and then the
> forked JVM exited.
> This caused the {{stdin}} buffer could not be read completely.
> The completion of JVM could not be marked in master process in Maven and
> therefore it was considered as a serious JVM error.
> Version {{2.19.2}} implemented acknowledgement of JVM exit by sending
> {{BYE_ACK}} command from master to the fork.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SUREFIRE-1342) Acknowledge normal exit of JVM and drain shared memory between processes
[ https://issues.apache.org/jira/browse/SUREFIRE-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1342: --- Affects Version/s: 2.19.1 > Acknowledge normal exit of JVM and drain shared memory between processes > > > Key: SUREFIRE-1342 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1342 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Affects Versions: 2.19.1 >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (SUREFIRE-1342) Acknowledge normal exit of JVM and drain shared memory between processes
[ https://issues.apache.org/jira/browse/SUREFIRE-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1342. -- > Acknowledge normal exit of JVM and drain shared memory between processes > > > Key: SUREFIRE-1342 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1342 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SUREFIRE-1342) Acknowledge normal exit of JVM and drain shared memory between processes
[ https://issues.apache.org/jira/browse/SUREFIRE-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana resolved SUREFIRE-1342. Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=da7ff6aa25a72094705c24981afbf8294ac4b1dc > Acknowledge normal exit of JVM and drain shared memory between processes > > > Key: SUREFIRE-1342 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1342 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6199) Maven does not attempt to reconnect reset connections
[
https://issues.apache.org/jira/browse/MNG-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949679#comment-15949679
]
Michael Osipov commented on MNG-6199:
-
I am very much convinced that this is a problem with your NAT and/or Atlassian
Pipelines and I will tell you why:
Nature of HTTP/1.1 connections in connection with Apache HttpClient: all HTTP
connections are persistent and can be left open for an indefinite amount of
time unless either client or server say {{Connection: close}}. HttpClient will
pool connections until the aforementioned event will happen. If one side closes
the connection, it remains stale and the peer has no way to detect that
reliably.
[Here|https://blog.fastmail.com/2011/06/28/http-keep-alive-connection-timeouts/]
and
[there|https://hc.apache.org/httpcomponents-client-ga/tutorial/html/connmgmt.html]
are good reads on your issue. Closing connections is none of your NAT's
business.
How to tackle this issue: first of all, download Maven 3.5.0-beta-1, it
includes an all new Maven Wagon version which can have logging be enabled on
the *shaded* HttpClient. Read
[this|https://hc.apache.org/httpcomponents-client-ga/logging.html] and enable
"best for debugging". You'll see all request/response headers and even more
important the pool management and how long are connections kept in the pool.
Share them here.
Counter measures: HttpClient offers a lot of config params how connections are
treated which are not exposed via Wagon because no one ever needed them. What
you can try immediately is to pass
{{-Dmaven.wagon.http.pool=false}}/{{-Dhttp.keepAlive=false}} or set request
header {{Connection: close}} (performance degregation) in your {{settings.xml}}.
{{PoolingHttpClientConnectionManager}} offers a lot of other possibilities to
solve your issue. Let's see how we get with the stuff above first.
> Maven does not attempt to reconnect reset connections
> -
>
> Key: MNG-6199
> URL: https://issues.apache.org/jira/browse/MNG-6199
> Project: Maven
> Issue Type: Bug
>Reporter: Martin Myslík
>
> I was recently discussing and issue with Atlassian team concerning failing
> build on Atlassian Pipelines when running Maven build for more than 5 minutes.
> The issue was with NAT timeout which kills all idle connections after 5
> mintues and Maven does not try to reconnect once the connection is killed
> (and hence cannot download artifacts from Maven central).
> Please, take a look at the open issue (it contains more detailed description
> and also comments from Atlassian which suggested opening an issue with
> Maven):
> https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections
> Could you, please, take a minute and explain how could proceed with solving
> this issue? I am not sure whether this is something that Maven should handle
> or whether it is Atlassians issue.
> Thank you for your input.
> This is the link to my public repo with test project running tests for 15
> mintues. This build fails on Pipelines because of Maven connection that is
> being killed during the test: https://bitbucket.org/Smedzlatko/del-me
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MNG-6199) Maven does not attempt to reconnect reset connections
[ https://issues.apache.org/jira/browse/MNG-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948957#comment-15948957 ] Thomas Turrell-Croft commented on MNG-6199: --- Log message of example failed build. https://bitbucket.org/Smedzlatko/del-me/addon/pipelines/home#!/results/%7B43b830ef-0047-44d0-9020-f2f1695b00d6%7D The example has a test which simply put the current thread to sleep. The full stack trace: Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:2.6:jar (default-jar) on project del-me: Execution default-jar of goal org.apache.maven.plugins:maven-jar-plugin:2.6:jar failed: Plugin org.apache.maven.plugins:maven-jar-plugin:2.6 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-jar-plugin:jar:2.6 -> org.apache.maven:maven-core:jar:2.2.1 -> org.apache.maven.reporting:maven-reporting-api:jar:2.2.1: Failed to read artifact descriptor for org.apache.maven.reporting:maven-reporting-api:jar:2.2.1: Could not transfer artifact org.apache.maven.reporting:maven-reporting-api:pom:2.2.1 from/to central (https://repo.maven.apache.org/maven2): Connection reset -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:2.6:jar (default-jar) on project del-me: Execution default-jar of goal org.apache.maven.plugins:maven-jar-plugin:2.6:jar failed: Plugin org.apache.maven.plugins:maven-jar-plugin:2.6 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-jar-plugin:jar:2.6 -> org.apache.maven:maven-core:jar:2.2.1 -> org.apache.maven.reporting:maven-reporting-api:jar:2.2.1 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-jar of goal org.apache.maven.plugins:maven-jar-plugin:2.6:jar failed: Plugin org.apache.maven.plugins:maven-jar-plugin:2.6 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-jar-plugin:jar:2.6 -> org.apache.maven:maven-core:jar:2.2.1 -> org.apache.maven.reporting:maven-reporting-api:jar:2.2.1 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 20 more Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-jar-plugin:2.6 or one of its dependencies could not be resolved: Failed to collect dependencies at org.apache.maven.plugins:maven-jar-plugin:jar:2.6 -> org.apache.maven:maven-core:jar:2.2.1 -> org.apache.maven.reporting:maven-reporting-api:jar:2.2.1 at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolveInternal(DefaultPluginDependenciesResolver.java:214) at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:149) at
[jira] [Updated] (MNG-6199) Maven does not attempt to reconnect reset connections
[ https://issues.apache.org/jira/browse/MNG-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Myslík updated MNG-6199: --- Description: I was recently discussing and issue with Atlassian team concerning failing build on Atlassian Pipelines when running Maven build for more than 5 minutes. The issue was with NAT timeout which kills all idle connections after 5 mintues and Maven does not try to reconnect once the connection is killed (and hence cannot download artifacts from Maven central). Please, take a look at the open issue (it contains more detailed description and also comments from Atlassian which suggested opening an issue with Maven): https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections Could you, please, take a minute and explain how could proceed with solving this issue? I am not sure whether this is something that Maven should handle or whether it is Atlassians issue. Thank you for your input. This is the link to my public repo with test project running tests for 15 mintues. This build fails on Pipelines because of Maven connection that is being killed during the test: https://bitbucket.org/Smedzlatko/del-me was: I was recently discussing and issue with Atlassian team concerning failing build on Atlassian Pipelines when running Maven build for more than 5 minutes. The issue was with NAT timeout which kills all idle connections after 5 mintues and Maven does not try to reconnect once the connection is killed (and hence cannot download artifacts from Maven central). Please, take a look at the open issue (it contains more detailed description and also comments from Atlassian which suggested opening an issue with Maven): https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections Could you, please, take a minute and explain how could proceed with solving this issue? I am not sure whether this is something that Maven should handle or whether it is Atlassians issue. Thank you for your input. > Maven does not attempt to reconnect reset connections > - > > Key: MNG-6199 > URL: https://issues.apache.org/jira/browse/MNG-6199 > Project: Maven > Issue Type: Bug >Reporter: Martin Myslík > > I was recently discussing and issue with Atlassian team concerning failing > build on Atlassian Pipelines when running Maven build for more than 5 minutes. > The issue was with NAT timeout which kills all idle connections after 5 > mintues and Maven does not try to reconnect once the connection is killed > (and hence cannot download artifacts from Maven central). > Please, take a look at the open issue (it contains more detailed description > and also comments from Atlassian which suggested opening an issue with > Maven): > https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections > Could you, please, take a minute and explain how could proceed with solving > this issue? I am not sure whether this is something that Maven should handle > or whether it is Atlassians issue. > Thank you for your input. > This is the link to my public repo with test project running tests for 15 > mintues. This build fails on Pipelines because of Maven connection that is > being killed during the test: https://bitbucket.org/Smedzlatko/del-me -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6199) Maven does not attempt to reconnect reset connections
[ https://issues.apache.org/jira/browse/MNG-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948630#comment-15948630 ] Martin Myslík commented on MNG-6199: It is happening on Atlassian Pipelines (https://confluence.atlassian.com/bitbucket/bitbucket-pipelines-792496469.html). But the issue is generally with AWS NAT configuration and Maven not being able to handle connections that are killed by it. I am basically running 'mvn install' which first donwloads all necessary dependencies, runs tests for 15 mintues and then triggers an additional phase which needs more artifacts from Maven central but the build fails because the connection has been killed in the meantime. I am able to make it work by using 'mvn -Dmaven.wagon.http.pool=false clean install' but that just seems like a dirty hack. > Maven does not attempt to reconnect reset connections > - > > Key: MNG-6199 > URL: https://issues.apache.org/jira/browse/MNG-6199 > Project: Maven > Issue Type: Bug >Reporter: Martin Myslík > > I was recently discussing and issue with Atlassian team concerning failing > build on Atlassian Pipelines when running Maven build for more than 5 minutes. > The issue was with NAT timeout which kills all idle connections after 5 > mintues and Maven does not try to reconnect once the connection is killed > (and hence cannot download artifacts from Maven central). > Please, take a look at the open issue (it contains more detailed description > and also comments from Atlassian which suggested opening an issue with > Maven): > https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections > Could you, please, take a minute and explain how could proceed with solving > this issue? I am not sure whether this is something that Maven should handle > or whether it is Atlassians issue. > Thank you for your input. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6199) Maven does not attempt to reconnect reset connections
[ https://issues.apache.org/jira/browse/MNG-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948615#comment-15948615 ] Karl Heinz Marbaise commented on MNG-6199: -- Is this happening on an open source project? Cause you are using Maven central directly ? > Maven does not attempt to reconnect reset connections > - > > Key: MNG-6199 > URL: https://issues.apache.org/jira/browse/MNG-6199 > Project: Maven > Issue Type: Bug >Reporter: Martin Myslík > > I was recently discussing and issue with Atlassian team concerning failing > build on Atlassian Pipelines when running Maven build for more than 5 minutes. > The issue was with NAT timeout which kills all idle connections after 5 > mintues and Maven does not try to reconnect once the connection is killed > (and hence cannot download artifacts from Maven central). > Please, take a look at the open issue (it contains more detailed description > and also comments from Atlassian which suggested opening an issue with > Maven): > https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections > Could you, please, take a minute and explain how could proceed with solving > this issue? I am not sure whether this is something that Maven should handle > or whether it is Atlassians issue. > Thank you for your input. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MNG-6199) Maven does not attempt to reconnect reset connections
Martin Myslík created MNG-6199: -- Summary: Maven does not attempt to reconnect reset connections Key: MNG-6199 URL: https://issues.apache.org/jira/browse/MNG-6199 Project: Maven Issue Type: Bug Reporter: Martin Myslík I was recently discussing and issue with Atlassian team concerning failing build on Atlassian Pipelines when running Maven build for more than 5 minutes. The issue was with NAT timeout which kills all idle connections after 5 mintues and Maven does not try to reconnect once the connection is killed (and hence cannot download artifacts from Maven central). Please, take a look at the open issue (it contains more detailed description and also comments from Atlassian which suggested opening an issue with Maven): https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections Could you, please, take a minute and explain how could proceed with solving this issue? I am not sure whether this is something that Maven should handle or whether it is Atlassians issue. Thank you for your input. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6196) Updated Mockito, slf4j and logback dependences to latest versions
[ https://issues.apache.org/jira/browse/MNG-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15948489#comment-15948489 ] Hervé Boutemy commented on MNG-6196: I'd prefer to wait for 3.5.0 release: there is no hurry and I would not appreciate if there is some unexpected change associated to the slf4j update (like System.out cache impact, and so on) > Updated Mockito, slf4j and logback dependences to latest versions > - > > Key: MNG-6196 > URL: https://issues.apache.org/jira/browse/MNG-6196 > Project: Maven > Issue Type: Improvement > Components: Dependencies >Affects Versions: 3.5.0-beta-1 >Reporter: Sylwester Lachiewicz >Priority: Minor > > Update dependences for maven build > Mocito 1.10 -> 2.7.19 > Slf4j 1.7.22 -> 1.7.25 (SLF4J-394) > logback-classic 1.2.2 > With slf4j update we can simplify maven-slf4j-provider implementation -- This message was sent by Atlassian JIRA (v6.3.15#6346)
