Hmmm...I can't imagine a scenario where that makes sense, but I can't
say there isn't one. The WAR is created already. I just need to launch
Jetty (or some other container) to run the WAR, then run the test suite
against the container.
I actually got this working - sort of. I'm not happy with it, yet,
though. As far as I can tell, the Jetty plugin "run-war" goal doesn't
support the capability to provide a jetty-env.xml file the way the
jetty:run goal does. Maybe it's just not documented, but I couldn't
make it work, either. So, I ended up running the exploded directory
from my integration-test module by referring to the other module's
directories. (Like I said, I'm not very happy with it.)
I'd love to see a good example of something like this. I'm sure someone
has solved this problem in a more "Maven" kind of way. I plan to have a
look at Selenium over the weekend as a possible option.
Rusty Wright wrote:
Would it make sense for the integration test make its own war? The
jetty plugin docs say for webApp:
defaults to ${project.build.directory}/${project.build.finalName}.war
David C. Hicks wrote:
Oh yuck! That looked a whole lot better when I clicked the "Send"
button. Hopefully, this is more readable...
David C. Hicks wrote:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.11</version>
<configuration>
<webApp>
<<something refering to the sibling artifact WAR file goes here>>
</webApp>
</configuration>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
