You got it Robert.. Robert Mark Bram wrote on 07.10.2014 19:59:
> OK, this was very helpful too. In this case, I am working with a > multi-module project and I decided it was best to add our selenium > tests in a new project to keep them away from other project code. We > have 13 pom.xml files, not counting the one I am adding. So this is my > next challenge, to ensure I get this project executing after the > others have done their job and deployed to the app server. In order to make that happen you test module just has to declare a dependency to the ear or whatever is the final output that will be deployed and tested in the module. The reactor (e.g. multi module support in Maven) will then do the right thing. manfred --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
