[mailto:p...@hammant.org]
Sent: Saturday, October 13, 2018 9:00 AM
To: Maven Users List
Subject: [SUSPICIOUS] Re: [SUSPICIOUS] Re: Running integration tests twice
against different webapp configurations
You're explicitly calling stop() on both Jetty instances ... (pass or fail) and
not just letting it
already started," even with a different
> key and port.
>
> Thanks,
> Scott
>
> -Original Message-
> From: Thomas Broyer [mailto:t.bro...@gmail.com]
> Sent: Friday, October 12, 2018 2:34 AM
> To: Maven Users List
> Subject: [SUSPICIOUS] Re: Running
instance in the same vm fails with error
"ShutdownMonitor already started," even with a different key and port.
Thanks,
Scott
-Original Message-
From: Thomas Broyer [mailto:t.bro...@gmail.com]
Sent: Friday, October 12, 2018 2:34 AM
To: Maven Users List
Subject: [SUSPICIOUS] R
There's Cuppa which is super cool and allows to control such things to a
very fine level.
https://github.com/cuppa-framework/cuppa/
It is not clear that Cuppa has multi-year life though. I wish it did.
On Thu, Oct 11, 2018 at 10:21 PM Ellis, Scott
wrote:
> Hi,
>
> I have a project that builds
Alternatively, if possible, you could possibly run the app with both
configurations in parallel (two executions of jetty-maven-plugin in
pre-integration-test and post-integration-test phase, using different
ports), and run you tests twice, for each app / port (two executions of
failsafe at integrat
I'd say you need two modules; one for each IT setup. Each module is a Maven
project and will then run the integration tests. The actual integration
test code could then be in a third module and you declare a dependency on
that artifact.
/Anders
On Thu, Oct 11, 2018 at 11:21 PM Ellis, Scott
wrote
_
> From: Martin Gainty
> Sent: Tuesday, May 30, 2017 7:08:43 PM
> To: Maven Users List
> Subject: Re: Running integration tests against a signed jar
>
>
>
>
> From: Gary Gregory
> Sent: Monday, May 29, 2017 5:01 PM
> To: Ma
domains on the
server or is this only signing for protecting the archives?
Gruss
Bernd
--
http://bernd.eckenfels.net
From: Martin Gainty
Sent: Tuesday, May 30, 2017 7:08:43 PM
To: Maven Users List
Subject: Re: Running integration tests against a signed jar
From: Gary Gregory
Sent: Monday, May 29, 2017 5:01 PM
To: Maven Users List
Subject: Running integration tests against a signed jar
Hi All:
I have a POM that builds a signed jar, so far so good. Unit tests run, no
problem.
When integration tests run through fai
Hi Robert,
On 10/6/14 11:31 AM, Robert Mark Bram wrote:
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-sure
Thanks Anders...
It can be hard to look that stuff on the phone...
I remember wanting to have a symmetry with the Surefire patterns of
Test*.java; *Test.java; *TestCase.java but I couldn't recall what I did for
the last one!
On 8 October 2014 07:19, Anders Hammar wrote:
> >
> > So failsafe wil
>
> So failsafe will pickup
>
> ITblahblah.java
> BlahblahIT.java
>
> And a third form that I forget
>
*ITCase.java
http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html#includes
/Anders
>
>
> >
> >
> > > > 3) Run integration tests after compile?
> > > > The real re
Then all I ask is you pay your newfound enlightenment forward...
With this information you can answer some maven newbie questions on the M/L
On Wednesday, 8 October 2014, Robert Mark Bram
wrote:
> Thank you Stephen - this was very useful and came just when I am ready
> to start piecing together
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,
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 var
On 6 October 2014 10:31, Robert Mark Bram wrote:
> 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
> mave
http://docs.codehaus.org/plugins/servlet/mobile#content/view/63286
On May 15, 2014 10:14 PM, "Brendan Miller" wrote:
> I currently have some testng integration tests in a maven project. This is
> causing problems because the tests get picked up and run during the test
> phase, rather than the in
You need to add/bind the maven-failsafe-plugin to your build:
http://maven.apache.org/surefire/maven-failsafe-plugin/usage.html
You also need to adapt the naming of your test files:
http://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html
/Anders
On Thu, May 8, 2
ject for this, since I'd like them
more closely associated with the project it's testing, but could do it
as a last resort.
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Friday, May 13, 2005 10:56 AM
To: 'Maven Users List'
Subject: RE: Run
> -Original Message-
> From: Thomas Van de Velde [mailto:[EMAIL PROTECTED]
> Sent: vendredi 13 mai 2005 20:01
> To: Maven Users List
> Subject: Re: Running integration tests
>
> Vincent,
>
> Any plans on building Cargo support for WAS?
Definitely... as soon
> -Original Message-
> From: Thomas Van de Velde [mailto:[EMAIL PROTECTED]
> Sent: vendredi 13 mai 2005 20:01
> To: Maven Users List
> Subject: Re: Running integration tests
>
> Vincent,
>
> Any plans on building Cargo support for WAS?
Definitely... as soon
Vincent,
Any plans on building Cargo support for WAS?
Cheers,
Thomas
On 5/13/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
>
>
>
> > -Original Message-
> > From: David Jackman [mailto:[EMAIL PROTECTED]
> > Sent: vendredi 13 mai 2005 18:32
> > To: Maven Users List
> > Subject: Running
> -Original Message-
> From: David Jackman [mailto:[EMAIL PROTECTED]
> Sent: vendredi 13 mai 2005 18:32
> To: Maven Users List
> Subject: Running integration tests
>
> For one of my projects, I need to add some integration tests that are
> separate from the unit tests. The unit tests wo
> -Original Message-
> From: David Jackman [mailto:[EMAIL PROTECTED]
> Sent: vendredi 13 mai 2005 18:32
> To: Maven Users List
> Subject: Running integration tests
>
> For one of my projects, I need to add some integration tests that are
> separate from the unit tests. The unit tests wo
You integration project surely depends on the main project.
that is why when ever you make changes in main project
you must run jar:install to place its jar into local respository
and the integration to pickit up automatically.
Also, when ever you have to multiple projects collabrating together,
Thanks Dan.
I set up a separate project as you suggested, which includes a
dependency on the main project.
This works fine, but it requires me to jar:install my main project each
time I run the integration tests.
So I'd like to make the integration tests a subproject and add a
dependency on th
I was hoping for something like this (which doesn't work BTW :-)
// maven.xml
Any ideas?
Cheers,
-Ralph.
On 02.03.2005, at 19:02, dan tran wrote:
Ralph,
I would add another project to house your integration test cases.
The source of the testcase must stay in
Ralph,
I would add another project to house your integration test cases.
The source of the testcase must stay in the main source directory.
(not the unit test src)
After that, use jelly/java to drive your integration in maven.xml
-D
On Wed, 2 Mar 2005 17:42:31 +0100, Ralph Pöllath <[EMAIL PR
28 matches
Mail list logo
