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.
UPDATE 2011-05-30
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.
Related posts:
Posted by digulla 
Dark Views 
When Laziness Gets Expensive
9. May, 2011According to heise online (German, video in English), Professor Dr. Eugene Spafford estimates the costs Sony‘s EPIC FAIL to secure their PSN servers to be 21 billion dollars.
Wow. 21 … fucking … BILLION … dollars. That’s 70’000’000 PS3s. 70 million PS3s. 36 million iPhone 4s. 700’000 cars at $30’000/each. They must be doing pretty well to be able to afford such a loss.
And it’s not that they didn’t see it coming. Sony knew for months that their servers were outdated and missing crucial security patches. Well, someone decided that it wasn’t worth to fix that. So: EPIC FAIL. Again. And again. Will they ever learn?
That feels like the same arrogance which led to the lawsuit against geohot and graf_chokolo. Which probably made someone on the Internet so angry that they decided to give Sony this wedgy. Message to Sony: It’s not smart to be arrogant in the face of overwhelming odds.
You have, say, 1’000 people working to protect your assets. The world has a population of 7 billion (and you just lost 3 dollars to every and each of them) and the probability that one of them can kick you where it really hurts is about 1. At least.
Of course, the company is now using all its power to hunt down the little bastard. Sony, if you read this: Don’t be surprised if a 13-year old kid outwitted your whole security team.
Or rather the manager, who told the team not to fix those servers. But no, managers are never wrong. So the team must be punished. Fire them! All of them! Without supper! Serves them right! And don’t forget to sue the kid! Sue him to hell! Make sure he is not allowed to touch an electronic device ever again. EVER! It’s not your fault what happened! Try to create more DMCA-like laws! So you can sue more people! Get your engineering team to build a time traveling device so you can sue in advance! Force parents to divorce so they can’t breed anything threatening your revenue! Show the world who’s boss! Dictatorships never worked before but that should not stop you! It should rather encourage you! Grow by setting challenging goals!
See where the leads and why you can never win?
Making the world-wide security community hate you even more is your best bet! Trust me, I know at least as well as the guy who created this mess. And you trusted him, didn’t you?
Share this: