I've been looking at the aerogear-controller-demo and noticed that there were a few dependencies I had not expected. The war contains the following:
WEB-INF/lib/aerogear-controller-1.0-SNAPSHOT.jar WEB-INF/lib/aerogear-haml-1.0-SNAPSHOT.jar WEB-INF/lib/cglib-nodep-2.2.jar WEB-INF/lib/guava-r07.jar WEB-INF/lib/hamcrest-core-1.3.RC2.jar WEB-INF/lib/hamcrest-generator-1.3.RC2.jar WEB-INF/lib/hamcrest-integration-1.3.RC2.jar WEB-INF/lib/hamcrest-library-1.3.RC2.jar WEB-INF/lib/iogi-0.9.1.jar WEB-INF/lib/javax.servlet-api-3.0.1.jar WEB-INF/lib/jmock-2.5.1.jar WEB-INF/lib/jmock-legacy-2.5.1.jar WEB-INF/lib/jruby-complete-1.6.7.jar WEB-INF/lib/mirror-1.5.1.jar WEB-INF/lib/objenesis-1.0.jar WEB-INF/lib/paranamer-2.2.jar WEB-INF/lib/qdox-1.6.1.jar
Specifically the hamcrest and jmock libraries stood out which are pulled in by 'br.com.caelum:iogi', which is a compile scope dependency of aerogear-controller.
I've tried adding an exclude to aerogear-controller/pom.xml and the demo still works without these deps, but since Aerogear is very new to me chances are I'm missing something.
Let me know if this looks alright and I'll issue a pull request.
Qmx is traveling today, and he was one that developed the aerogear-controller prototype. I agree with you thought if we can lighted the dependencies I'm all for it.
Since the demo kept working with exclude I'm guess this is just some extra baggage. Or some planned items that are TODO's.
Qmx will know for sure.