Hi all again, I solved the issue, indeed it had nothing to do with Maven specifically, but with the JVM. It was using IPv6 as default for all the applications using Java, so I specified to use IPv4 instead (at config level in the .zshrc file, adding *export JDK_JAVA_OPTIONS="-Djava.net.preferIPv4Stack=true*") and in the Anypoint Studio.ini file (adding *-Djava.net.preferIPv4Stack=true* to the vmargs).
Sorry for the inconvenience and thanks for the help! Ana El mar, 8 oct 2024 a las 11:12, Michael Osipov (<micha...@apache.org>) escribió: > I don't see a Maven issue here at all. This is purely network. gnodet@ > has reported that GHA fails with Maven Central recently as well. > > On 2024/10/07 08:00:15 Ana Roig Jimenez wrote: > > Hi everyone, > > > > I am writing to seek assistance with an issue I encountered when I > started > > running Maven commands on my project (the final objective is to use > > Anypoint Studio to work with Mulesoft, which uses Maven) - I'll try to > add > > as much context and information as I can in this email. > > For several days, I have been unable to execute basic Maven commands such > > as *mvn** clean test *even in a minimal pom.xml. Despite having a minimal > > pom.xml configuration without any dependencies (attached the *pom.xml* > I'm > > now using for testing), I consistently encounter the following error > (this > > one after executing mvn clean test): > > > > > > > > [*INFO*] Scanning for projects... > > > > [*INFO*] > > > > [*INFO*] *--------------------< *com.javatpoint:CubeGenerator* > > >--------------------* > > > > [*INFO*] *Building CubeGenerator 1.0-SNAPSHOT* > > > > [*INFO*] from pom.xml > > > > [*INFO*] *--------------------------------[ jar > > ]---------------------------------* > > > > Downloading from central: https://repo.maven.apache.org/maven2/ > > > org/apache/maven/plugins/maven-surefire-plugin/3.2.5/maven-surefire-plugin-3.2.5.pom > > > > [*INFO*] > > > *------------------------------------------------------------------------* > > > > [*INFO*] *BUILD FAILURE* > > > > [*INFO*] > > > *------------------------------------------------------------------------* > > > > [*INFO*] Total time: 0.319 s > > > > [*INFO*] Finished at: 2024-10-04T09:47:28+02:00 > > > > [*INFO*] > > > *------------------------------------------------------------------------* > > > > [*ERROR*] Plugin org.apache.maven.plugins:maven-surefire-plugin:3.2.5 or > > one of its dependencies could not be resolved: > > > > [*ERROR*] The following artifacts could not be resolved: > > org.apache.maven.plugins:maven-surefire-plugin:pom:3.2.5 (absent): Could > > not transfer artifact > > org.apache.maven.plugins:maven-surefire-plugin:pom:3.2.5 from/to central > ( > > https://repo.maven.apache.org/maven2): Broken pipe > > > > [*ERROR*] -> *[Help 1]* > > > > [*ERROR*] > > > > [*ERROR*] To see the full stack trace of the errors, re-run Maven with > the > > *-e* switch. > > > > [*ERROR*] Re-run Maven using the *-X* switch to enable full debug > logging. > > > > [*ERROR*] > > > > [*ERROR*] For more information about the errors and possible solutions, > > please read the following articles: > > > > [*ERROR*] *[Help 1]* > > > http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException > > > > It always shows the *Broken pipe* at the end, regardless of the plugin it > > tries to find, so I'm thinking it might be more related to connections, > > secure certifications, or something like that, but couldn't find a > > definitive answer through the Internet, nor the AI. > > > > > > I have uninstalled and reinstalled Maven (I'm using SDKMAN) and removed > all > > the dependencies of the pom.xml to begin with something simple (as you > can > > see in the screenshot, although it still tries to download things from > > https://repo.maven.apache.org/maven2), however, it didn't solve > anything. > > > > Given that this issue has persisted across several attempts and appears > to > > impact different artifacts, as I said, it may be related to connectivity > or > > repository access. I want to mention that my two colleagues, who have the > > same work computer, don't have any issues with Maven and can work with > > Mulesoft successfully. We work with VPN but the issue continues even > after > > deactivating it. > > Another information I believe is relevant to mention is that I > encountered > > this 'Broken pipe' issue as well when working in IntelliJ at the > beginning > > of the year (when I tried to get the latest updates), and when I > contacted > > support, after several solutions they tried to give me, we solved it > adding > > the parameter -Djava.net.preferIPv4Stack=true in Help | Edit Custom VM > > Options. > > > > Here are some details about my environment: > > Maven Version: 3.9.9 > > Operating System: macOS Sonoma 14.5 (aarch64) M1 Pro > > Java SDK Version: 17 (I downgraded it because my colleagues use this one) > > > > If there are any specific logs or additional information you require, > > please let me know, and I will provide them promptly. I would greatly > > appreciate your guidance and support to resolve this matter because it's > > blocking my work. > > > > Thank you in advance for your support. > > Ana > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
