One if the best features in
Maven is dependency management. Even with its known problems it is a great step forward and
many other build systems reuse Maven's repository structure.
One of the essential parts of this vision is the Maven Central Repository, your one stop shop for most of the dependencies in your projects.
Publishing to Maven Central has always had its requirement set (you can find an updated list
here), one of them being that the repository must be self-contained. That is, no artifact may depend on another artifact that is not part of the repository.
Back in 2008, when I started both
derquinsej and
lucis, this requirement was fulfilled with no problem and synchronization with Central was provided thanks to
Sourceforge's SSH access.
However, as time passed, some projects such as Hibernate starting publishing its artifacts in external repositories and many other interesting projects were hosted in repositories different of Central, such as Java.net. So, for future projects Central Publishing was not an option and I prepared an
external repository for my own projects.
Fortunately, the situation has improved a lot:
- Now many interesting external repositories, such as JBoss and Java.net, are synchronized back in Central.
- Central navigation and search has been enhanced.
- Sonatype provides a repository for open source projects with the option of being published in Central. The process is very well documented and the response is fast and great (kudos to Juven Xu).
So, from now on, you can find
Derquinse Commons in
Maven Central.