The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Just to repeat myself: IDEs are wonderful, but I always recommend you have a way of building in batch.
First and foremost, I've discovered over the years that the average developer maintains a lot of context in their IDE that doesn't get propagated out to version control. So if I take someone else's project and import it, I can easily spend a day+ getting it to build in my installation of the identical IDE. This is assuming that everyone's using the same IDE. For batch builds, it's mostly a matter of acquiring and additional canned external libraries the project needs - which is something Maven can do automatically.
Secondly, IDEs tend to change significantly between releases, Very often (more like inevitably, for Microsoft IDEs I've worked with), the build process will break. More time lost.
Thirdly, IDEs require a lot of resources. If you want to raise the odds that you can build in an emergency when things are going wrong, a batch build is easier to set up and more likely to work.
Finally, in my environments, the actual production builds are done on a machine that lacks a GUI. No GUI, no IDE. Not a problem for batch builders.
This is not to say I'm anti-GUI. Try and take away my IDE and you'll lose fingers. However, I always try and have an offline build option - generally Ant or Maven.
An IDE is no substitute for an Intelligent Developer.