Please, if you're starting a new Java project, and have any say at all in the build process, don't use Maven. Go with Ant. You'll thank yourself later, and anyone else who ever has to build the project will also thank you.
Personally, I can't begin to describe the awfulness of Maven in words. I'd sooner use makefiles and shell scripts, or manually type in build commands written in pen on a stack of notecards.
But you don't have to take my word for it; here's an SO discussion about how much Maven sucks:
http://stackoverflow.com/questions/861382/why-does-maven-hav...
Re:HTTP+JSON Services in Modern Java
by sandGorgon on Saturday March 02, 2013 @11:24PM
(#5312516)
interesting - so did you decouple dependency management from tge build process and still use maven/ivy for that part?
This would be another blog post by itself. In short: build a fat jar with maven, package with arx, run with runit.
Most projects use Junit and Easymock.
I work in a Ruby + Java shop and we do Java deployments with maven + nexus + capistrano. Works like a champ.
I'll see if I have some time to write a blogpost about it.
Re:HTTP+JSON Services in Modern Java
by sandGorgon on Saturday March 02, 2013 @09:46AM
(#5309606)
that would be great ! do talk about which app server (tomcat, jetty, etc.)
are you using maven, etc.? I would be very interested to find out how a ruby centric dev shop is handling Java deployments and builds.
P. S. how about mocks and testing?