I have a web application with 20 dependencies that we write in house. Those 20 dependencies each add new functionality to the web application.
For example. Lets say the web application is a zoo, and the 20 dependencies are 5 exhibits and 15 animals where animals reside within exhibits. Each exhibit and animal has their own web resources (jsp, js, css, images) and java classes. At build time, maven reaches into each of the modules and pull up the web resources into the web application's target. So this application is assembled 100% at build time.
In order to add a new animal, I have to develop the new jar, tell the web app's pom all about the new animal module and how to get the web resources. I have to build a whole new war and redeploy the war to the server.
What I would like to be able to do is have a web app that runs and to be able to add new exhibits and animals to the application\WEB-INF\lib and see the new features added to the web application.