On Aug 27, 2010, at 6:34 AM, Thomas Sundberg wrote:
> Assume that we are dealing with a multi module build, how would you
> organize the modules? Would you consider adding a separate
> 'integration-test' tree next to main and test?
I set it up like so:
parent module
|-- domain cl
will run in memory and as fast as possible.
I define integration tests as tests that are dependent on other
resources than the source code. This is (at least):
* The file system
* Databases
* Network access
Assume that we are dealing with a multi module build, how would you
organize the modules
I don't know how interested they are in messing with their 'version 6'
branch, though some of us are glued to it at the moment. I can but
ask. I keep wishing that Maven itself had more ways that profile (b)
could turn off things from the base or a previous profile (a).
On Tue, Aug 24, 2010 at 10:5
> problem. However, the maven-jetty-plugin lacks a 'skip' property. I
>
> Anyone got another suggestion?
Add/request the skip property for m-jetty-p? Should be super simple to do.
Wayne
-
To unsubscribe, e-mail: users-unsubscr..
some integration tests in
the release process. I can turn off the failsafe execution, not a
problem. However, the maven-jetty-plugin lacks a 'skip' property. I
moved the whole business into a profile, but ! doesn't work in the
release plugin profile list, and -P! doesn't work
run different type
of tests, e.g merge coverage of unit and integration tests
+) I would assume that you can create your instrumented libraries using
M2 profiles
Cheers,
Siegfried Goeschl
Douglas Ferguson wrote:
> Is there anyway to get code coverage numbers for integration tests?
&g
jects in a similar fashion, but I wasn't quite satisfied by the number of
> manual steps still involved), but it's a start...
>
>
> On 27-01-10 18:44, Wendy Smoak wrote:
>>
>> On Wed, Jan 27, 2010 at 10:07 AM, Douglas Ferguson
>> wrote:
>>
>>>
ps still involved), but it's a start...
On 27-01-10 18:44, Wendy Smoak wrote:
On Wed, Jan 27, 2010 at 10:07 AM, Douglas Ferguson
wrote:
Is there anyway to get code coverage numbers for integration tests?
I'm sure it's technically possible, but as far as I know, no one has
done i
On Wed, Jan 27, 2010 at 10:07 AM, Douglas Ferguson
wrote:
> Is there anyway to get code coverage numbers for integration tests?
I'm sure it's technically possible, but as far as I know, no one has
done it yet with Maven. It's definitely on my list of things I'd like
to s
Is there anyway to get code coverage numbers for integration tests?
D/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[Off Topic]
Don't run "mvn integration-test" as the post-integration-test will never be
executed, instead run "mvn verify" (and it's shorter to type)
2010/1/25 Jacek Furmankiewicz
> We have a fairly complex set of integration tests that rely on embedded
> Je
We have a fairly complex set of integration tests that rely on embedded
Jetty and a JNDI setup file we provide for it.
In that file we have references to external resources via relative file
paths.
This works great if we run "mvn integration test" from that project folder.
However, i
> > > >> structure.
> > > >>
> > > >> So my question remains. How would you suggest that the integration
> > > >> testing is fitted into the modules?
> > > >
> > > > This depends on how and when you want to fail th
the integration
> > >> testing is fitted into the modules?
> > >
> > > This depends on how and when you want to fail the build and what you
> > > class as integration testing.
> > >
> > > An example.
> > >
> > > I have a war module.
>
ends on how and when you want to fail the build and what you
> > class as integration testing.
> >
> > An example.
> >
> > I have a war module.
> >
> > Best practice is to keep the java classes in a separate module.
> >
> > That java module dep
l the build and what you
> class as integration testing.
>
> An example.
>
> I have a war module.
>
> Best practice is to keep the java classes in a separate module.
>
> That java module depends on other java modules.
>
> I have unit tests in each java module. IMHO, unit
e java classes in a separate module.
That java module depends on other java modules.
I have unit tests in each java module. IMHO, unit tests should not
depend on anything else. They use, e.g. mock database connections,
and they mock out the other java modules.
I have class 1 integration tests
on
testing is fitted into the modules?
/Thomas
As a sidenote, I totally agree with the quote from Dijkstra.
>
> 2009/9/23 Thomas Sundberg
>
> > Hi!
> >
> > I'm about to set up en fresh project using Maven. It will contain a web
> > part
> > that will be
contain a ear part and it will contain
> integration tests. How would you suggest organising it?
>
> I'm thinking on the lines of:
>
> root --
> -- ear [Mostly packaging for a application server]
>
> -- war -- src -- main -- java ...
>-
Hi!
I'm about to set up en fresh project using Maven. It will contain a web part
that will be a war, it will contain a ear part and it will contain
integration tests. How would you suggest organising it?
I'm thinking on the lines of:
root --
-- ear [Mostly packaging for a a
e failsafe site
(http://mojo.codehaus.org/failsafe-maven-plugin/xref/index.html)
in both
the IntegrationMojo and VerifyMojo classes shows parameters for the
skipTests etc, but not one for skipITs.
--
View this message in context:
http://www.nabble.com/How-to-skip-integration-tests-tp23870998p243
e-maven-plugin/xref/index.html) in both
>>> the IntegrationMojo and VerifyMojo classes shows parameters for the
>>> skipTests etc, but not one for skipITs.
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-skip-i
> ben.lidgey wrote:
>>>
>>> I can't get this to work. Looking in the code on the failsafe site
>>> (http://mojo.codehaus.org/failsafe-maven-plugin/xref/index.html) in both
>>> the IntegrationMojo and VerifyMojo classes shows parameters for the
>>> skipTests
-plugin/xref/index.html) in both
>> the IntegrationMojo and VerifyMojo classes shows parameters for the
>> skipTests etc, but not one for skipITs.
>>
>
> --
> View this message in context:
> http://www.nabble.com/How-to-skip-integration-tests-tp23
he failsafe site
> (http://mojo.codehaus.org/failsafe-maven-plugin/xref/index.html) in both
> the IntegrationMojo and VerifyMojo classes shows parameters for the
> skipTests etc, but not one for skipITs.
>
--
View this message in context:
http://www.nabble.com/How-to-skip-integration-te
can I skip only the integration
tests? The only way I could see to do it is to put the failsafe plugin in a
separate profile in the pom, and activate that profile when I want to run
the integration tests.
BTW, the failsafe version is 2.4.3-alpha-1 and maven 2.0.10.
Ben
Stephen Connolly-2 wrote:
&g
If you use failsafe-maven-plugin to run your integration tests then
-DskipITs
will skip only the integration tests (i.e. failsafe tests only)
-DskipTests
will skip the surefire and failsafe tests
while
-Dmaven.test.skip=true
will skip compiling the tests as well as running them (surefire or
e you tested and it doesn't work? I normally keep the integration
tests in a separate module and therefore haven't had the need to be
able to turn them off.
/Anders
On Thu, Jun 4, 2009 at 07:17, Farrukh Najmi
wrote:
> Hi Guys,
>
> I see that specifying -Dmaven.test.skip=tr
Hi Guys,
I see that specifying -Dmaven.test.skip=true skips units tests vut does
not skip integration tests.
Is there a way to specify an option to skip integration tests? If not,
is there an open issue to request
a way to do this? Thanks for your help.
--
Regards,
Farrukh
Web: http
I agree: if you haven't changed any code, and you haven't changed any unit
tests, then the only tests that need to run are the integration tests that
you are changing. If you've made a mistake and have changed application or
unit test code, your CI process will (should) pick it up
On Wed, Feb 4, 2009 at 1:46 PM, John Cartwright
wrote:
> Hello All,
>
> could someone suggest a recommendation or best practice for configuring the
> pom.xml to separate the unit and integration tests? I'd like to be able to
> run the unit tests independently of the integr
suggest a recommendation or best practice for configuring the
> pom.xml to separate the unit and integration tests? I'd like to be able to
> run the unit tests independently of the integration tests.
>
> Thanks!
>
> --john
>
>
> -
Hello All,
could someone suggest a recommendation or best practice for configuring
the pom.xml to separate the unit and integration tests? I'd like to be
able to run the unit tests independently of the integration tests.
Thanks!
-
008/11/27 Kristof Vanbecelaere <[EMAIL PROTECTED]>
> >>
> >> Actually, that is the aim.
> >>
> >> You run all the unit tests to make sure that the code is good enough to
> >> try
> >> and run the integration tests.
> >>
>
e
> without unit tests.
>
>
> Stephen Connolly-2 wrote:
>>
>> 2008/11/27 Kristof Vanbecelaere <[EMAIL PROTECTED]>
>>
>> Actually, that is the aim.
>>
>> You run all the unit tests to make sure that the code is good enough to
>> try
>> an
It is possible to just run unit tests or integration tests from a module but it
gets messy and over complicated.
For example I have projects that separate tests by placing all unit tests in a
directory called unit and all integration tests in a directory called it.
With such a separation it
tof Vanbecelaere <[EMAIL PROTECTED]>
>
> Actually, that is the aim.
>
> You run all the unit tests to make sure that the code is good enough to
> try
> and run the integration tests.
>
> If your unit tests fail, your code is broken and you know it, so fix your
> co
cely.
>
> - John
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/maven-surefire-plugin-configuration-for-unit-integration-tests-
And if you really just want to run integration tests pull these out
into their own module which contains no unit tests.
Hand-running the integration-test goal will also work well, if there's
just one. Or a profile would work nicely.
-
>> Unfortunately, I failed to make it work. When running mvn integration-test
>> all unit tests get to run before running the integration tests, which is
>> not
>> really the aim. The idea really is to be able to either run unit tests or
>> integration tests but
all unit tests get to run before running the integration tests, which is
> not
> really the aim. The idea really is to be able to either run unit tests or
> integration tests but not both at the same time. Any ideas why this fails?
>
Actually, that is the aim.
You run all the unit tests to
Hello,
I found this interesting blog:
http://weblogs.java.net/blog/johnsmart/archive/2008/06/unit_tests_are.html
Unfortunately, I failed to make it work. When running mvn integration-test
all unit tests get to run before running the integration tests, which is not
really the aim. The idea
is the project itself and
> the second one is the integration-tests. I have cobertura reports for
> unit tests execution, but, is there any way to have cobertura reports
> for integration tests execution?
>
> Thanks in advance.
> Carlos
>
> ---
I am facing a similar problem. Had no time to attack it now, but as far
as some googling told me, it's a bit of a problem with maven &
cobertura, better is emma & maven, because it's easier to both switch
instrumentation on in emma and merge the result files of the integrati
Hi all
I have a bi-module project, the first module is the project itself and
the second one is the integration-tests. I have cobertura reports for
unit tests execution, but, is there any way to have cobertura reports
for integration tests execution?
Thanks in advance.
Carlos
jects in your big
project (e.g. EAR1 and EAR2)?
i have seen some maven examples that create a separate project for
integration testsmy assumption is that
EAR1 is in project EAR1 and EAR2 is in project EAR2...
you could create a test project that includes both EAR1 and EAR2 that
contains your
-module2
doc
tools
etc
And let's say the main project generates RPM:s which actually include a full
bundled J2EE server (JBoss)
Now, what if I would like to have integration tests that do:
1 - Install RPM:s
2 - Start J2EE server (and hence the application)
3 - Configure th
Hi, yes i dont wanted to
- place the integration-tests in a different module - thats because we
already have up to 15 modules in our multi-module-build and I guess our
developers won´t be happy if I move their tests around the world:-)
- rename all the tests afterwards and introduce naming
Hmm yes, but Torsten said that was exactly what he wanted to avoid. In
addition to naming conventions for unit & integration tests, we use a
separate module for our heavier, end-to-end functional tests.
Kalle
On Thu, May 29, 2008 at 10:06 AM, Paul Davis <[EMAIL PROTECTED]> wrote:
Another option is to place the integration tests into a separate module.
On Thu, May 29, 2008 at 8:12 AM, Kalle Korhonen <[EMAIL PROTECTED]>
wrote:
> Standard answer is with naming convention, see
> http://www.mail-archive.com/users@maven.apache.org/msg81355.html.
>
> Kalle
Standard answer is with naming convention, see
http://www.mail-archive.com/users@maven.apache.org/msg81355.html.
Kalle
On Thu, May 29, 2008 at 7:54 AM, <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Actually, we have mixed JUnit Testcases in our modules - some of them can
> be run "standalone" with no dat
Hi,
Actually, we have mixed JUnit Testcases in our modules - some of them can
be run "standalone" with no database connection or any other environment,
others need environment.
I now want to separate those tests into different categories, but I don´t
want to
- manually create a DatabaseTestS
I'm working on a project using JPA, and since the project is a framework, it is
strictly standard JPA with no proprietary code for any particular JPA provider.
I have an extensive set of integration tests which unfortunately fail in one
place or another depending on which JPA provi
Hi Kalle!
On Monday 07 April 2008 Kalle Korhonen wrote:
> Just change the packaging type temporarily from pom to jar and run mvn
> eclipse:eclipse.
That's what I do right now, but IMHO that's not a solution for the problem
but rather a workaround.
Thanks anyway and best regards,
- martin
sign
Just change the packaging type temporarily from pom to jar and run mvn
eclipse:eclipse. That said; we keep our integration tests with the modules
and use naming conventions to differentiate between them and "pure" unit
tests.
Kalle
On Mon, Apr 7, 2008 at 6:22 AM, Martin Höller <[EM
Ping! Nobody using the maven-eclipse-plugin with integration test modules?
On Friday 04 April 2008 Martin Höller wrote:
> Hi!
>
> According to a wiki article [0], the two maven books, and some mails on
> this list it is best practice to put integration tests in one (or
> multiple)
Hi!
According to a wiki article [0], the two maven books, and some mails on this
list it is best practice to put integration tests in one (or multiple)
separate module(s). In all examples I could find, this IT-module is of
packaging type pom, which IMO makes sense as I wouldn't need a JAR
maven-surefire-plugin
**/*UnitTest.java
surefire-it
integration-test
See this posting:
http://mail-archives.apache.org/mod_mbox/maven-users/200801.mbox/[EMAIL
PROTECTED]
Paul
On Wed, Feb 27, 2008 at 11:06 AM, Luca Marrocco <[EMAIL PROTECTED]>
wrote:
> 2008/2/27, vitor lundberg <[EMAIL PROTECTED]>:
> > I wish that my integration test start after the "package" st
2008/2/27, vitor lundberg <[EMAIL PROTECTED]>:
> I wish that my integration test start after the "package" steep.
> so if I put my classes under the same repertory as the tests classes maven
> dont make the differences
> that is a way to make a difference thoses tests ?
i havent tried this fe
Thx for replay Luc,
but the problem is if I create my integration test under src/test/java my
integration test will starts like a unit test under the lifecyle "test" and
I wish that my integration test start after the "package" steep.
so if I put my classes under the same repertory as the tests c
Hi Vitor,
the simplest way is to create you integration test as junit classes
under src/test/java directory.
Luca
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
hello,
in the maven lifecycle we have the integration tests.
Can some one help me to understand how to implement thoses tests ??
thx,
Vitor
On Nov 12, 2007 5:49 PM, mfs <[EMAIL PROTECTED]> wrote:
> Can "java/src/test" be used to package both unit and integration tests ? Or
> this structure specifically for the unit test-cases.. ?
Yes, but -- in a separate module.
Maven does not currently support normal unit
On 11/12/07, mfs <[EMAIL PROTECTED]> wrote:
>
> Can "java/src/test" be used to package both unit and integration tests
> ? Or
> this structure specifically for the unit test-cases.. ?
Yes, it can be used for both. Typically you'd name your pure unit tests as
Guys,
Can "java/src/test" be used to package both unit and integration tests ? Or
this structure specifically for the unit test-cases.. ?
Like for example in my case we have an html file used for some
functional/integration testing, would it be a good idea to put it in the
java/src/t
I'm beginning to think this is impossible in Maven2:
Suppose I want to use Cargo, Selenium, and Cobertura to get a coverage
number in a web application, but I don't want the process to interfere
with a Continuum build on a headless Linux box.
I'm so tangled up in the mass of configuration fil
And you were perfectly right, my integration tests compile now !! Thanks
a lot for your help.
For the record, I did as you advised me, that is :
- I added a "foojar" module and moved the source code from "foowar"
there
- I made "foowar" depend on "foojar"
On 5/21/07, Arnaud Jeansen <[EMAIL PROTECTED]> wrote:
My problem is that I can't make these integration tests compile in the
"test" phase of the "integtesttomcat" module. These tests depend on the
classes from foowar/src/main/java (to compile test classes looki
o tutorial)
Integtesttomcat : comes after deploytomcat in the parent pom "modules"
section, the goal is to run the "test" phase with my integration tests
(using integtesttomcat/src/it). These tests require that the application
is properly deployed, they will basically test the webservices.
Because we need to define the test source code location in one place,
, in the POM, will adding both a unit tests
location and an integration tests location in a element
work to include both the unit tests and integration tests source code,
like shown below? Thank you.
${basedir}/src/alltests
Thank you, much appreciated. I will use the solution in the post.
Thank you.
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this messa
On 5/6/07, Morgovsky, Alexander (US - Glen Mills)
<[EMAIL PROTECTED]> wrote:
May someone please tell me what I need to add to the POM to run
integration tests? In which element do I need to declare the location
of the integration test .java files? Which plugin do I need to add to
the s
May someone please tell me what I need to add to the POM to run
integration tests? In which element do I need to declare the location
of the integration test .java files? Which plugin do I need to add to
the section to run the integration tests? Thanks.
This message (including any
, 2007 12:11 PM
> To: Maven Users List
> Subject: Re: [m2] Integration-test target runs integration tests
> twice...
>
> FYI for the future... Next time, use "mvn help:effective-pom" to help
> diagnose problems like this.
>
> Wayne
>
> On 2/19/07, EJ Ciramel
plugin for more details.
>
> Cheers!
> Nap
>
> On 3/28/07, raju <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi Kalle,
>>
>> Thanks for the link.I have some doubts:
>>
>> Does cargo plug-ins actually run or has ability to run the integration
t;[EMAIL PROTECTED]> wrote:
Hi Kalle,
Thanks for the link.I have some doubts:
Does cargo plug-ins actually run or has ability to run the integration
tests
or it just starts the servers,deploys the war containing the tests?
Sorry if the question sounded out of context.
I am asking the above quest
Hi Kalle,
Thanks for the link.I have some doubts:
Does cargo plug-ins actually run or has ability to run the integration tests
or it just starts the servers,deploys the war containing the tests?
Sorry if the question sounded out of context.
I am asking the above question because i was
http://svn.codehaus.org/trails/trunk/trails/examples/simple/pom.xml
Kalle
On 3/27/07, raju <[EMAIL PROTECTED]> wrote:
Hi,
I need to build and deploy Junit Integration tests to weblogic and run the
integration tests.I think cargo plug-in helps one achieve that.
A sample pom file to a
Hi,
I need to build and deploy Junit Integration tests to weblogic and run the
integration tests.I think cargo plug-in helps one achieve that.
A sample pom file to achieve this would be of great help.Server could be
anything.
Once deployed as a war i need to invoke the tests using the webapp
You can put the integration test's in a profile, and not
activate that profile when you release. You'll have to update the
version number for that module since the release plugin won't do it
for you.
Yes it's possible to use profiles but it would be better to have a
configuration as discus
On 3/1/07, Dan Adams <[EMAIL PROTECTED]> wrote:
I have a project that is a jar library with the following structure:
/
/lib
/integration-tests
/web
/tests
I want to release it but I don't want to deploy the integration-test
module or check it's dependecies for sn
I have a project that is a jar library with the following structure:
/
/lib
/integration-tests
/web
/tests
I want to release it but I don't want to deploy the integration-test
module or check it's dependecies for snapshots and such. Can I ignore it
using the release plugin
ne Fay [mailto:[EMAIL PROTECTED]
Sent: Monday, February 19, 2007 12:11 PM
To: Maven Users List
Subject: Re: [m2] Integration-test target runs integration tests
twice...
FYI for the future... Next time, use "mvn help:effective-pom" to help
diagnose problems like this.
Wayne
On 2/19/07, EJ
ng (which works flawlessly).
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Monday, February 19, 2007 12:11 PM
To: Maven Users List
Subject: Re: [m2] Integration-test target runs integration tests
twice...
FYI for the future... Next time, use "mvn help:effective-p
FYI for the future... Next time, use "mvn help:effective-pom" to help
diagnose problems like this.
Wayne
On 2/19/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
Ok, so I seem to have found out why this is happening. At the top most
pom, we have a minor surefire configuration (we'd like all the uni
2007 1:39 PM
To: Maven Users List
Subject: RE: [m2] Integration-test target runs integration tests
twice...
Those configuration options are for surefire, not maven.
-Original Message-
From: Bashar Abdul Jawad [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 15, 2007 11:39 AM
To: &
So? Surefire plugin is what runs the tests.
Bashar
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 15, 2007 11:39 AM
To: Maven Users List
Subject: RE: [m2] Integration-test target runs integration tests twice...
Those configuration options are
Those configuration options are for surefire, not maven.
-Original Message-
From: Bashar Abdul Jawad [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 15, 2007 11:39 AM
To: 'Maven Users List'
Subject: RE: [m2] Integration-test target runs integration tests
twice...
They a
false
>
> **/*ITest.java
>
>
>
>
>
>
>
>
>
Bashar
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 15, 2007 7:35 AM
To: Maven Users List
Subject: RE: [m2] Integration-test targ
To me these look the same, can you point out where I went wrong?
-Original Message-
From: Bashar Abdul Jawad [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 2:47 PM
To: 'Maven Users List'
Subject: RE: [m2] Integration-test target runs integration tests
twice...
To: 'Maven Users List'
Subject: RE: [m2] Integration-test target runs integration tests twice...
Hi,
This is not a bug, your pom is not configured correctly.
Try this in your POM file:
org.apache.maven.plugins
maven-suref
14, 2007 8:20 AM
To: Maven Users List
Subject: RE: [m2] Integration-test target runs integration tests twice...
Sorry I had that backward a bit, integration tests should only run the
*Itest.java files. The regular test phase should only include the
Utest.java files.
We can get the unit tests to
See:
MNG-2826
Done...
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 1:47 PM
To: Maven Users List
Subject: RE: Integration-test target runs integration tests twice...
Which requires a login
Sigh
Signing up for yet
Which requires a login
Sigh
Signing up for yet another maven related item
-Original Message-
From: franz see [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 11:07 AM
To: users@maven.apache.org
Subject: RE: Integration-test target runs integration tests twice
0, Time elapsed: 25.23
> sec
>
> Results :
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 14, 2007 10:20 AM
> To: Maven Users List
> Subject: RE: [m
ed: 0, Time elapsed: 25.23
sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 10:20 AM
To: Maven Users List
Subject: RE: [m2] Integration-test target runs integration tests
Sorry I had that backward a bit, integration tests should only run the
*Itest.java files. The regular test phase should only include the
Utest.java files.
We can get the unit tests to run fine, it's the integration tests run
via integration-test that run twice.
-Original Message-
al works fine, but when you
specify "integration-test" it runs the *Utest.java tests twice.
I'll attach the logs shortly...
-Original Message-
From: franz see [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 13, 2007 9:51 PM
To: users@maven.apache.org
Subject: Re: [m2] In
Good day to you, EJ,
What happens twice? ...May I ask for the build logs in your console?
Cheers,
Franz
EJ Ciramella-2 wrote:
>
> I'm having a problem binding our integration tests to the
> integration-test lifecycle goal.
>
> Can anyone explain why this would happen tw
101 - 200 of 293 matches
Mail list logo
