I’ve recreated the testing repository using the latest version of my Maven Tools 4 Eclipse.
To browse the repository, please use the Nexus interface.
If you pull in any dependencies from the repository, non-Eclipse artifacts will come from from Project Orbit. If you want non-Eclipse dependencies (like log4j) from Maven Central, you need to change your profiles.
Deactivate “m4e.orbit” and activate “m4e.maven-central“. From the command line, that’s “-P m4e.maven-central” but I suggest to put these into your settings.xml (add “<activeProfile>m4e.maven-central</activeProfile>” to it).
Note that you don’t need to deactivate the profile m4e.orbit. As soon as you specify a profile on the command line or via the settings, it’s deactivated automatically.
“mvn help:active-profiles” and “mvn dependency:tree” are your friends.
Let me know if you find anything missing, odd, broken by filing a bug or posting a comment here.
Some dependencies from the new repo can also be found on Maven Central. One nasty problem is that both repos contain org.eclipse.equinox.app but the version from Maven Central contains odd dependencies which break your build.
To fix this, add this to your parent/root POM:
<dependencyManagement> <dependencies> <dependency> <groupId>org.eclipse.dash</groupId> <artifactId>dependency-management</artifactId> <version>3.6.2</version> <type>pom</type> <scope>import</scope> </dependency> <dependencies> <dependencyManagement>
This will limit all version ranges to the versions found in our new repository. Since Maven Central didn’t import new versions for at least one year, this should fix all problems.