After investigations in #32, maven doesn't appear to be the appropriate tool for the job. It simply does too much.

Looking into groovy's grape system (with a default resolution engine backed by ivy), ivy is much more suited for the job. First and foremost, it is a dependency management tool. This means we are getting a much smaller dependency as a lot of the unneeded extras provided by maven are not included. Secondly we still get all of the dependency management that we want out of shrinkwrap but with a more extensible API.

I believe that this switch could actually be a backwards compatible change thanks to IvyConvertPom. Since this might take some time it won't make it into the 1.2.0 release.