Community
Participate
Working Groups
Within the last couple months, potentially as of the Jenkins upgrade yesterday, an older pipeline we have was broken as we cannot find a repo for m2e. The location being pointed at is http://download.eclipse.org/technology/m2e/releases. Also noticed there is not a compositeContent.xml for this directory and wondered if perhaps something was missed during the upgrade. Below is the stack trace for the error: [INFO] Adding repository http://download.eclipse.org/technology/m2e/releases [ERROR] Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'm2e' from location http://download.eclipse.org/technology/m2e/releases: No repository found at http://download.eclipse.org/technology/m2e/releases. -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'm2e' from location http://download.eclipse.org/technology/m2e/releases at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) 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: java.lang.RuntimeException: Failed to load p2 repository with ID 'm2e' from location http://download.eclipse.org/technology/m2e/releases
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.