On 9 October 2014 14:01, Robert Mark Bram wrote:
> > 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 lik
> 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 c
> 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?"
If the answer is "yes" then you will most likely need to deploy something
(pom) and that may require adding the missing
bindings into the lifecycle.
If the answer
Hi,
I would try to skip the deploy goal for this particular plugin
see http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
On Thu, Oct 9, 2014 at 10:23 AM, Robert Mark Bram <
robertmarkbram+mailing.li...@gmail.com> wrote:
> My parent POM declares this Selenium project in a profile
My parent POM declares this Selenium project in a profile.
default-build
true
FooProject-Model
FooProject-Thermal
FooProject-ViewController
FooProject-API-V1
FooProject-Monitoring
FooProject-ADF
