Hi all,
I am trying this command line:
mvn --fail-at-end -Plocal verify site
And I find that if an integration test fails, site is *not* being run
at all - even with --fail-at-end. This is my reporting element in
pom.xml:
reporting
plugins
plugin
Hi all,
Please excuse me if this is a double post - I couldn't be sure the
first one went through.
I am trying this command line:
mvn --fail-at-end -Plocal verify site
And I find that if an integration test fails, site is *not* being run
at all - even with --fail-at-end. This is my reporting
My parent POM declares this Selenium project in a profile.
profile
iddefault-build/id
!-- This profile will be active if another profile isn't triggered --
activation
activeByDefaulttrue/activeByDefault
/activation
modules
I would try to skip the deploy goal for this particular plugin
see http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
Ah, yes - this is what I needed. So still use jar packaging but skip
the deploy phase.
Rob
:)
Well the question you really will want to know is:
do I want any other modules to depend on the integration tests being
successful?
The Hatter opened his eyes very wide on hearing this; but all he said
was, Why is a mvn like a writing-desk?
If the answer is no then you will just configure
Thank you Stephen - this was very useful and came just when I am ready
to start piecing together this level of detail.
1) Default vs non-default plugins
suddenly a White Rabbit with pink eyes ran close by Alice
So, what I understood from this trip down the rabbit-hole.
- Maven defines
Hi All,
A couple of questions about integration tests..
1) Default vs non-default plugins
I needed to include the maven-failsafe-plugin plugin to introduce
integration tests into my project, but I didn't need to introduce the
maven-surefire-plugin to my pom.xml for unit tests. Fair enough, but
