Do you ever tried to upload an artifact to the central maven repository server? No? Well, that is not fun! The maven guys are pretty serious!
OK. If you want to upload something you “just” have to read this tutorial here:
AND this super long tutorial here:
On maven.apache.org they tell you that the most easiest way to upload something is over sonatype. You just have to create a user in their JIRA bug tracking tool and open a ticket! *LOL* Are you serious? Publishing software by opening a ticket in a bug tracking tool? Really? Reaaaaalllllyyyyyyyy?
Are you fu**ing kidding me?
And the best part is, that your ticket will be handled in just 2 business days. Wow.
No wonder that every company and even small open source teams are setting up their own Maven2 Repository.
To publish a open source project in RubyGems.org took me less than 5 min and it was published immediately. And I don’t know one single Ruby coder which is managing his own RubyGems Server.
8 thoughts on “Uploading Artifacts to the central maven repository”
We do not like the ruby guys. They take away another’s work and destroy the Maven administration. Long live the Maven administration and it’s complex processes, which saves a lot of jobs!
If it would be easy to upload artifacts to the central maven repo. server, nobody would by the Nexus Pro Repository Manager from Sonatype:
And nobody would buy training classes for Nexus:
That makes sens. 🙂
Install a complex process and sell expensive tools to solve the problem. 🙂
It works! Have a look on Microsoft, Oracle, IBM and SAP, for example.
You “should” review your business model for versioneye. It’s too easy to handel. “Easy” you can’t sell. 🙂
I agree with the first part. I disagree with the second part. I believe “Easy” you can sell pretty good 🙂
When you mean with “sell” giving it for free, then I am with you. Otherwise an example would be helpful.
I am sorry! Do not observe my first note. You’re right.
Example is coming soon 😉
Here is the example: http://www.versioneye.com/services