Maven 2 and the spring framework (or how to get your quick fix)

Although the maven repository often gets updated quite promptly sometimes us maven (ab)users get left out on a dry run and we have to wait for a uncertain period of time until our favorite lib gets uploaded to the repo. One of the more complex projects out there is the spring framework that even gets some special care by Carlos so that it gets in the repo as quickly as possible. What I wanted to point out to anyone that is waiting for the official inclusion to the repo is that now spring ships with an ant task that will copy the jar's in your repo, sweet!
ant mvn.install.jars

Submodules don't ship with a pom and declared dependencies (a shame but we'll get there one day, I hope) and also the required libs don't get copied to the repo as well. This is a bummer for some situations. I wanted to use the latest hibernate with JPA and for instance ibiblio doesn't have the latest hibernate entity manager that in turn has it's own nice set of dependencies that I would need to manually add to my repository. Why don't we all use maven and be happy? I understand how larger projects might be more fragile to build because of maven but, infrastructure libs should be obliged to ship with maven support by law (just kidding)! People bitch about maven2 these days, it is a pain in the ass sometimes but it has a mighty fine ROI for me and actually makes my use of your libraries easier, and you can always mix ant with maven if you need such a fine grained control like the contender suggest. As far as the reliability of the build process, a tool like Proximity might help, I'm waiting if the maven team will ship something of their own.
Anyhow I found this spring tip on the spring-osgi group on google groups so if you care about spring or osgi you might want to join it, it seems promising.

Comments

Popular posts from this blog

Relaxing SSL validation for JaxWS

Search and Replace in ODT using AODL

Kaspersky Anti Virus 6 and Subversion problems