The links provided by Sham HC are probably the most useful, especially the first. We are relatively new to AEM/CQ. The recommendation from our consultancy partner is to use the CQ Maven Blueprints archetype (multi-module), that is covered in the first link. I will warn you though, the parent POM described by that article is not the one that is produced when using the archetype to generate the project. We also experienced a few issues with some of the dependencies (esp: taglib) and are currently working through them.
We maintain our own parent POM (which is heavily based on the one in the article - albeit many of the dependency versions are updated) which points to our internal corporate Maven repo which proxies to the CQ Blueprints repo and Adobe public (you need to set those up in eClipse - but I assume you already know how to do that). So when you run the maven command you just substitute in your own URL ...
mvn archetype:generate -DarchetypeCatalog=<<URL to your corporate repo/proxy goes here>> -Dfilter=multi-module
HTHs
Fraser.
