Hi everyone,
We've got a multi-module Maven project producing a Java EE 7 war for Wildlfy 10.1, and we're using the wildfly-maven-plugin to run it.
For local testing purposes, we've got a (Maven) module with few addons which I'd like to prevent from ending up in the production war.
How can I achieve these goals?
- I only want to use mvn wildfly:run inside the webapp module.
- I don't want to rely on a separate Widlfly installation somewhere on the developer machine. I'm happy to include the local wildfly download/installation time the plugin requires.
- I want to be able to deploy above mentioned test addons locally (either as a jar or a separate war - I don't care as long as it does the job).
- As mentioned above, the main point is that whatever the solution is that the test code doesn't end up in the production war.
I really want to be able to work in a similar manner as described here, only with WildFly instead of TomEE.
