It is great that the Spring 2.0 jars are all in Maven. That makes development a bit easier for many of us. Thank you Ben.
However, unfortunately many of Spring's dependencies are not in the Maven repository. Or they are simply old versions not compatible with Spring anymore.
I've been running my own repository to which I upload things like toplink, hibernate, jotm, etc. But it is very annoying to maintain and to have that dependency on another repository.
How do people here deal with that? Do you just do the same or is there a better way?
Whether a project has good Maven support is also a big consideration when I put technologies together these days.
Another thing that annoy the **** out of me is the dependency nightmare that is still present in Maven. Some artifacts (including for example Spring MVC) suck in the world. Others depend on stuff that simply does not exist in the Maven repository.
Sorry for the little rant. I like Maven as tool to do builds, generate test reports and generate IDE project files. But when my projects get a little more complex than the average hello world example I quickly end up in complexity and non working builds.
How is that working out for other people?