Timothy Astle wrote:
...
Additionally, we have a Selenium grid set up. When our Jenkins build
system makes a build, cargo to grabs the war and failsafe runs our
selenium integration tests. All tests must pass before any artifact is
deployed to Nexus. So in a sense, it feels like cheating to
On 28/02/2013 9:32 AM, Olivier Lamy wrote:
2013/2/28 Timothy Astle :
I'll chime in here :) We create the artifact that we want, but we have two.
The WAR created by the maven war plugin, and the overlay war that is
standalone.
But we still need the war to package it in the standalone artifact.
2013/2/28 Timothy Astle :
> I'll chime in here :) We create the artifact that we want, but we have two.
> The WAR created by the maven war plugin, and the overlay war that is
> standalone.
But we still need the war to package it in the standalone artifact.
And all the logic to create a war is in t
I'll chime in here :) We create the artifact that we want, but we have
two. The WAR created by the maven war plugin, and the overlay war that
is standalone.
We were hoping to only deploy the tomcat overlay war since it does
everything that the other war does, plus contain tomcat. By doing t
2013/2/27 Richard McAleer :
> Hi,
> We're using tomcat7-maven-plugin 2.1 to build an executable war using the
> standalone-war-only goal. The maven build still generates the normal war
> file as well as the executable .war created by the plugin. However, since
> the standalone-war-only goal gener
Hi,
We're using tomcat7-maven-plugin 2.1 to build an executable war using
the standalone-war-only goal. The maven build still generates the
normal war file as well as the executable .war created by the plugin.
However, since the standalone-war-only goal generates a war that is both
executabl
