I have a standard multi-module maven WAR project that uses Spring.
parent.pom | --common.jar | ^ --models.jar | ^ --service.jar | ^ --web.war
The ^ shows how dependencies are structured. All modules have the same parent. This setup works great as you can have your classpath resources in the common module visible from the service module.
I have an .exe file that I want run
- from the tests of each module
- from the exploded war app
I also want the .exe to be bundled with the war relative to WEB-INF so that it can be accessed from the system once deployed.
What I do not want to do is:
- duplicate resources across modules
- set environment/system variables anywhere
- hardcode static system paths
- mock servlet context in tests
- tie the solution to a specific container
Ideally I would want all file path resolution to happen around the location of the WEB-INF folder for war deployment while doing something smart for junit tests in individual projects.
Finally, I want something that works both from cmd and Eclipse without doing some crazy Ecplise/Maven configuration with a multitude of different plugins.
Aucun commentaire:
Enregistrer un commentaire