[jira] [Commented] (MNG-6604) Intermittent failures while downloading GAVs from Nexus
[
https://issues.apache.org/jira/browse/MNG-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778654#comment-16778654
]
Michael Osipov commented on MNG-6604:
-
The issue is this {{Using the MultiThreadedBuilder implementation with a thread
count of 24}}. I guess you are hit by MRESOLVER-65. If so, I'd close this one
as duplicate and would ask you to add your information there.
> Intermittent failures while downloading GAVs from Nexus
> ---
>
> Key: MNG-6604
> URL: https://issues.apache.org/jira/browse/MNG-6604
> Project: Maven
> Issue Type: Bug
> Components: Command Line, Toolchains
>Affects Versions: 3.6.0
> Environment: Nexus OSS 3.15.2-01
> Docker 18.09.2 on Ubuntu 18.04.2 LTS
> Gitlab runner 11.8.0
>Reporter: Ivan Rizzante
>Priority: Major
> Attachments: docker-env.txt, log.txt
>
>
> Hello
> we're running maven 3.6.0 builds in a docker container and we use Nexus OSS
> configured as proxy for Maven Central.
> While running our builds using Gitlab CI, we're experiencing intermittent
> build failures because Maven cannot find artifacts in Nexus which we verified
> they are actually available.
> Error example below:
> {noformat}
> 20744 [main] [ERROR] Failed to execute goal on project EcotransitWSClient:
> Could not resolve dependencies for project
> it.sdb.ecotransit:EcotransitWSClient:jar:7.0.1-SNAPSHOT: Could not transfer
> artifact commons-beanutils:commons-beanutils:jar:1.9.3 from/to nexus
> (http://maven-repo.sdb.it:8081/repository/maven-public/):
> /builds/sdb/webportal/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar.part
> (No such file or directory) -> [Help 1]
> {noformat}
> I attached the full maven build log and our Docker env settings.
> We tried disabling the keep alive and also disabling the connection pooling
> but nothing seems to fix the issue.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6604) Intermittent failures while downloading GAVs from Nexus
[
https://issues.apache.org/jira/browse/MNG-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6604:
Description:
Hello
we're running maven 3.6.0 builds in a docker container and we use Nexus OSS
configured as proxy for Maven Central.
While running our builds using Gitlab CI, we're experiencing intermittent build
failures because Maven cannot find artifacts in Nexus which we verified they
are actually available.
Error example below:
{noformat}
20744 [main] [ERROR] Failed to execute goal on project EcotransitWSClient:
Could not resolve dependencies for project
it.sdb.ecotransit:EcotransitWSClient:jar:7.0.1-SNAPSHOT: Could not transfer
artifact commons-beanutils:commons-beanutils:jar:1.9.3 from/to nexus
(http://maven-repo.sdb.it:8081/repository/maven-public/):
/builds/sdb/webportal/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar.part
(No such file or directory) -> [Help 1]
{noformat}
I attached the full maven build log and our Docker env settings.
We tried disabling the keep alive and also disabling the connection pooling but
nothing seems to fix the issue.
was:
Hello
we're running maven 3.6.0 builds in a docker container and we use Nexus OSS
configured as proxy for Maven Central.
While running our builds using Gitlab CI, we're experiencing intermittent build
failures because Maven cannot find artifacts in Nexus which we verified they
are actually available.
Error example below:
{code:java}
20744 [main] [ERROR] Failed to execute goal on project EcotransitWSClient:
Could not resolve dependencies for project
it.sdb.ecotransit:EcotransitWSClient:jar:7.0.1-SNAPSHOT: Could not transfer
artifact commons-beanutils:commons-beanutils:jar:1.9.3 from/to nexus
(http://maven-repo.sdb.it:8081/repository/maven-public/):
/builds/sdb/webportal/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar.part
(No such file or directory) -> [Help 1]
{code}
I attached the full maven build log and our Docker env settings.
We tried disabling the keep alive and also disabling the connection pooling but
nothing seems to fix the issue.
> Intermittent failures while downloading GAVs from Nexus
> ---
>
> Key: MNG-6604
> URL: https://issues.apache.org/jira/browse/MNG-6604
> Project: Maven
> Issue Type: Bug
> Components: Command Line, Toolchains
>Affects Versions: 3.6.0
> Environment: Nexus OSS 3.15.2-01
> Docker 18.09.2 on Ubuntu 18.04.2 LTS
> Gitlab runner 11.8.0
>Reporter: Ivan Rizzante
>Priority: Major
> Attachments: docker-env.txt, log.txt
>
>
> Hello
> we're running maven 3.6.0 builds in a docker container and we use Nexus OSS
> configured as proxy for Maven Central.
> While running our builds using Gitlab CI, we're experiencing intermittent
> build failures because Maven cannot find artifacts in Nexus which we verified
> they are actually available.
> Error example below:
> {noformat}
> 20744 [main] [ERROR] Failed to execute goal on project EcotransitWSClient:
> Could not resolve dependencies for project
> it.sdb.ecotransit:EcotransitWSClient:jar:7.0.1-SNAPSHOT: Could not transfer
> artifact commons-beanutils:commons-beanutils:jar:1.9.3 from/to nexus
> (http://maven-repo.sdb.it:8081/repository/maven-public/):
> /builds/sdb/webportal/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar.part
> (No such file or directory) -> [Help 1]
> {noformat}
> I attached the full maven build log and our Docker env settings.
> We tried disabling the keep alive and also disabling the connection pooling
> but nothing seems to fix the issue.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1546) JUnit 5 runner does not honor JUnit 5 display names
[ https://issues.apache.org/jira/browse/SUREFIRE-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778576#comment-16778576 ] Tibor Digana commented on SUREFIRE-1546: [~gsoutter] Honestly we want to reopen this issue after SUREFIRE-1222 and add an extension to this plugin. The goal of this extension is to customize this behavior (alter ordinal/display names in XML and names of files or dirs). Every customer has opposite requirements. > JUnit 5 runner does not honor JUnit 5 display names > --- > > Key: SUREFIRE-1546 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1546 > Project: Maven Surefire > Issue Type: Bug > Components: JUnit 5.x support >Affects Versions: 2.22.0 >Reporter: Romain Manni-Bucau >Assignee: Tibor Digana >Priority: Major > Labels: junit5 > Fix For: 3.0.0-M4 > > Time Spent: 20m > Remaining Estimate: 0h > > JUnit 5 runner should respect the test @DisplayName instead of displaying the > classname if any is defined. Seems last release doesn't support that feature > of JUnit 5 making the console output and reports not the expected ones. > > Origin: https://github.com/junit-team/junit5/issues/990 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6603) XDG Base Directory Specification support
[ https://issues.apache.org/jira/browse/MNG-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien Nicoulaud updated MNG-6603: -- Description: Could Maven please follow the XDG Base Directory Specification for the configuration/data directory on linux? More infos here: * [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html] * [http://www.freedesktop.org/wiki/Software/pyxdg] * [https://wiki.archlinux.org/index.php/XDG_Base_Directory#Support] was: Could Maven please follow the XDG Base Directory Specification for the configuration/data directory on linux? More infos here: * [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html] * [http://www.freedesktop.org/wiki/Software/pyxdg] > XDG Base Directory Specification support > > > Key: MNG-6603 > URL: https://issues.apache.org/jira/browse/MNG-6603 > Project: Maven > Issue Type: Improvement > Components: Settings >Affects Versions: 3.6.0 >Reporter: Julien Nicoulaud >Priority: Major > Fix For: Issues to be reviewed for 4.x > > > Could Maven please follow the XDG Base Directory Specification for the > configuration/data directory on linux? > More infos here: > * [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html] > * [http://www.freedesktop.org/wiki/Software/pyxdg] > * [https://wiki.archlinux.org/index.php/XDG_Base_Directory#Support] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (MNG-6603) XDG Base Directory Specification support
[
https://issues.apache.org/jira/browse/MNG-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778213#comment-16778213
]
Michael Osipov edited comment on MNG-6603 at 2/26/19 5:20 PM:
--
This makes sense, I had lately the same idea for Windows using {{AppData}} with
{{Roaming}} and {{LocalLow}} for the repository.
All of this would require a change in code and behavior and pluggable locations
configurations. Likely not happen before 4.0.
was (Author: michael-o):
This makes sense, I had lately the same idea for Windows using {{AppData}} with
{{Roaming}} and {{LocalLow}} for the repository.
All of this would require a change in code and behavior and pluggable locations
configurations.
> XDG Base Directory Specification support
>
>
> Key: MNG-6603
> URL: https://issues.apache.org/jira/browse/MNG-6603
> Project: Maven
> Issue Type: Improvement
> Components: Settings
>Affects Versions: 3.6.0
>Reporter: Julien Nicoulaud
>Priority: Major
>
> Could Maven please follow the XDG Base Directory Specification for the
> configuration/data directory on linux?
> More infos here:
> * [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html]
> * [http://www.freedesktop.org/wiki/Software/pyxdg]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6603) XDG Base Directory Specification support
[ https://issues.apache.org/jira/browse/MNG-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MNG-6603: Fix Version/s: Issues to be reviewed for 4.x > XDG Base Directory Specification support > > > Key: MNG-6603 > URL: https://issues.apache.org/jira/browse/MNG-6603 > Project: Maven > Issue Type: Improvement > Components: Settings >Affects Versions: 3.6.0 >Reporter: Julien Nicoulaud >Priority: Major > Fix For: Issues to be reviewed for 4.x > > > Could Maven please follow the XDG Base Directory Specification for the > configuration/data directory on linux? > More infos here: > * [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html] > * [http://www.freedesktop.org/wiki/Software/pyxdg] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6603) XDG Base Directory Specification support
[
https://issues.apache.org/jira/browse/MNG-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778213#comment-16778213
]
Michael Osipov commented on MNG-6603:
-
This makes sense, I had lately the same idea for Windows using {{AppData}} with
{{Roaming}} and {{LocalLow}} for the repository.
All of this would require a change in code and behavior and pluggable locations
configurations.
> XDG Base Directory Specification support
>
>
> Key: MNG-6603
> URL: https://issues.apache.org/jira/browse/MNG-6603
> Project: Maven
> Issue Type: Improvement
> Components: Settings
>Affects Versions: 3.6.0
>Reporter: Julien Nicoulaud
>Priority: Major
>
> Could Maven please follow the XDG Base Directory Specification for the
> configuration/data directory on linux?
> More infos here:
> * [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html]
> * [http://www.freedesktop.org/wiki/Software/pyxdg]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MNG-6604) Intermittent failures while downloading GAVs from Nexus
[
https://issues.apache.org/jira/browse/MNG-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rizzante updated MNG-6604:
---
Description:
Hello
we're running maven 3.6.0 builds in a docker container and we use Nexus OSS
configured as proxy for Maven Central.
While running our builds using Gitlab CI, we're experiencing intermittent build
failures because Maven cannot find artifacts in Nexus which we verified they
are actually available.
Error example below:
{code:java}
20744 [main] [ERROR] Failed to execute goal on project EcotransitWSClient:
Could not resolve dependencies for project
it.sdb.ecotransit:EcotransitWSClient:jar:7.0.1-SNAPSHOT: Could not transfer
artifact commons-beanutils:commons-beanutils:jar:1.9.3 from/to nexus
(http://maven-repo.sdb.it:8081/repository/maven-public/):
/builds/sdb/webportal/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar.part
(No such file or directory) -> [Help 1]
{code}
I attached the full maven build log and our Docker env settings.
We tried disabling the keep alive and also disabling the connection pooling but
nothing seems to fix the issue.
was:
Hello
we're running maven 3.6.0 builds in a docker container and we use Nexus OSS
configured as proxy for Maven Central.
While running our builds using Gitlab CI, we're experiencing intermittent build
failures because Maven cannot find artifacts in Nexus which we verified they
are actually available.
Error example below:
{code:java}
20744 [main] [ERROR] Failed to execute goal on project EcotransitWSClient:
Could not resolve dependencies for project
it.sdb.ecotransit:EcotransitWSClient:jar:7.0.1-SNAPSHOT: Could not transfer
artifact commons-beanutils:commons-beanutils:jar:1.9.3 from/to nexus
(http://maven-repo.sdb.it:8081/repository/maven-public/):
/builds/sdb/webportal/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar.part
(No such file or directory) -> [Help 1]
{code}
I attached the full maven build log and our Docker env settings.
We tried disabling the keep alive (-{{Dhttp.keepAlive=false) and disabling
connection pooling but nothing seems to solve the issue}}
> Intermittent failures while downloading GAVs from Nexus
> ---
>
> Key: MNG-6604
> URL: https://issues.apache.org/jira/browse/MNG-6604
> Project: Maven
> Issue Type: Bug
> Components: Command Line, Toolchains
>Affects Versions: 3.6.0
> Environment: Nexus OSS 3.15.2-01
> Docker 18.09.2 on Ubuntu 18.04.2 LTS
> Gitlab runner 11.8.0
>Reporter: Ivan Rizzante
>Priority: Major
> Attachments: docker-env.txt, log.txt
>
>
> Hello
> we're running maven 3.6.0 builds in a docker container and we use Nexus OSS
> configured as proxy for Maven Central.
> While running our builds using Gitlab CI, we're experiencing intermittent
> build failures because Maven cannot find artifacts in Nexus which we verified
> they are actually available.
> Error example below:
> {code:java}
> 20744 [main] [ERROR] Failed to execute goal on project EcotransitWSClient:
> Could not resolve dependencies for project
> it.sdb.ecotransit:EcotransitWSClient:jar:7.0.1-SNAPSHOT: Could not transfer
> artifact commons-beanutils:commons-beanutils:jar:1.9.3 from/to nexus
> (http://maven-repo.sdb.it:8081/repository/maven-public/):
> /builds/sdb/webportal/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar.part
> (No such file or directory) -> [Help 1]
> {code}
> I attached the full maven build log and our Docker env settings.
> We tried disabling the keep alive and also disabling the connection pooling
> but nothing seems to fix the issue.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNG-6604) Intermittent failures while downloading GAVs from Nexus
Ivan Rizzante created MNG-6604:
--
Summary: Intermittent failures while downloading GAVs from Nexus
Key: MNG-6604
URL: https://issues.apache.org/jira/browse/MNG-6604
Project: Maven
Issue Type: Bug
Components: Command Line, Toolchains
Affects Versions: 3.6.0
Environment: Nexus OSS 3.15.2-01
Docker 18.09.2 on Ubuntu 18.04.2 LTS
Gitlab runner 11.8.0
Reporter: Ivan Rizzante
Attachments: docker-env.txt, log.txt
Hello
we're running maven 3.6.0 builds in a docker container and we use Nexus OSS
configured as proxy for Maven Central.
While running our builds using Gitlab CI, we're experiencing intermittent build
failures because Maven cannot find artifacts in Nexus which we verified they
are actually available.
Error example below:
{code:java}
20744 [main] [ERROR] Failed to execute goal on project EcotransitWSClient:
Could not resolve dependencies for project
it.sdb.ecotransit:EcotransitWSClient:jar:7.0.1-SNAPSHOT: Could not transfer
artifact commons-beanutils:commons-beanutils:jar:1.9.3 from/to nexus
(http://maven-repo.sdb.it:8081/repository/maven-public/):
/builds/sdb/webportal/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar.part
(No such file or directory) -> [Help 1]
{code}
I attached the full maven build log and our Docker env settings.
We tried disabling the keep alive (-{{Dhttp.keepAlive=false) and disabling
connection pooling but nothing seems to solve the issue}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6603) XDG Base Directory Specification support
[
https://issues.apache.org/jira/browse/MNG-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777919#comment-16777919
]
Julien Nicoulaud commented on MNG-6603:
---
Currently a workaround is:
{code:xml}
mvn -gs "$XDG_CONFIG_HOME"/maven/settings.xml{code}
With {{settings.xml}}:
{code:xml}
http://maven.apache.org/SETTINGS/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
https://maven.apache.org/xsd/settings-1.0.0.xsd";>
...
${env.XDG_CACHE_HOME}/maven/repository
...
{code}
> XDG Base Directory Specification support
>
>
> Key: MNG-6603
> URL: https://issues.apache.org/jira/browse/MNG-6603
> Project: Maven
> Issue Type: Improvement
> Components: Settings
>Affects Versions: 3.6.0
>Reporter: Julien Nicoulaud
>Priority: Major
>
> Could Maven please follow the XDG Base Directory Specification for the
> configuration/data directory on linux?
> More infos here:
> * [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html]
> * [http://www.freedesktop.org/wiki/Software/pyxdg]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNG-6603) XDG Base Directory Specification support
Julien Nicoulaud created MNG-6603: - Summary: XDG Base Directory Specification support Key: MNG-6603 URL: https://issues.apache.org/jira/browse/MNG-6603 Project: Maven Issue Type: Improvement Components: Settings Affects Versions: 3.6.0 Reporter: Julien Nicoulaud Could Maven please follow the XDG Base Directory Specification for the configuration/data directory on linux? More infos here: * [http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html] * [http://www.freedesktop.org/wiki/Software/pyxdg] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Mazorius commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli
Mazorius commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36#issuecomment-467435360 Hi @khmarbaise , did you know when the next release will be build? I will currently try to use a snapshot but it would be nice if we got a official release version. Thanks @sparsick for your fix! ;) This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] Mazorius commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli
Mazorius commented on issue #36: [MENFORCER-142] documentation - add example for checking rules via cli URL: https://github.com/apache/maven-enforcer/pull/36#issuecomment-467435360 Hi @khmarbaise , did you know when the next release will be build? I will currently try to use a snapshot but it would be nice if we got a official release version. Thanks @sparsick for your fix! ;) This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
