The proper solution is to manage the scope of your dependencies.
In the jar project, the dependencies are place in compile scope, this is ok, because a jar does not add the dependencies when packaging
In the war project, the dependencies are placed in providedCompile scope. This allows me to compile my war, but not to package my libaries.
In my root of my project I have my ear build file. In this build file I have re-added all the dependencies (this still feels wrong because I have defined my dependencies twice) with the earLib scope. By doing so, my dependencies are place in root of my project in my defined lib folder.