Option one:
You could have one separate project for each integration layer?
I was just looking into something like, I just arrived in a project.. want
to run the integration tests... then I could just do:
cd /proper-integration-directory
mvn integration-tests
mvn tests:integration-tests
optio
Fork the book on github and write the update. Send a pull request and I
will work with your for whatever else is necessary.
Manfred
On Mon, September 17, 2012 3:48 pm, John Riedl wrote:
> And *that* was exactly what I needed. Thank you very much for your
> help. It turns out the lifecycle.xml
And *that* was exactly what I needed. Thank you very much for your
help. It turns out the lifecycle.xml was fine, but I needed *both* a
LifecycleMapping component *and* a Lifecycle component. I had
discovered examples with each separately on the web, but this is the
first example I've seen with
Reading your mail, I seem to understand your problem is not a real one.
You have a multimodule project, running A module, then B.
A fails during tests, then you are surprised that B build does not even
start.
If so, then it's working as expected.
If you want tests to not fail your whole build (s
I believe that this is the correct behaviour.
The Parent pom has a dependencyManagement section where you can put the
versions of libraries that you want to use but this does not push
dependencies into child POMs.
This is a good thing since we have about 60 POMs that share a parent and
do not w
Hi
I'm trying to use the assembly plugin to build a product distribution. I
include a parent POM declaration in my POM. The parent POM has many
dependencies (mixed scope: compile, provided and test)
When I execute make-assembly the resulting distribution does not contain the
dependent artifa
I would suggest that you make sure that your tests are idempotent
(http://geekswithblogs.net/dthakur/archive/2004/11/19/15282.aspx) and
independent and deterministic. This will not only allow you to run tests
in parallel, but it will also help maintainability a lot.
It is also a red flag that you
thx guys for your comments..
yes we have integration tests included in the build.
I have tried running them parallel but the tests are not atomic so are not
working as expected.
we have some DB call where we are using thread sleep,is there anything by
which this can be improved
Also we have any bes
> I am implementing Maven for the build Automation and as well as Test Run.
> Now i have two different projects and i have created one Parent Project to
> build both of them.
> But now some error is coming when i am running parent pom.xml.
> Its Building only single Module.
> And after running Test
I understand your point, and agree that I might be nice to have a bit more
of a standard place for integration tests. However, one point that should
be mentioned is that there are frequently multiple levels of integration
tests (in container, out of container, ui, etc). Thus it might not be so
si
Use the Failsafe plugin, though a separate module is good practice too:
http://maven.apache.org/plugins/maven-failsafe-plugin/
Danny
-Original Message-
From: Clebert Suconic [mailto:clebert.suco...@gmail.com]
Sent: 17 September 2012 14:05
To: Maven Users List
Subject: Re: Improving proje
That's one thing I always thought that maven should have an explicit
spot for integration tests. We also had to create a separate profile.
Having them into a more standard place would make it cleaner IMO.
That's a feature request I know. But does it make sense?
Sent from my iPhone
On Sep 17, 201
Simone,
You're right, this is a limitation of artifact produced by profiles. Unless
you can live with classifier computed from the running platform.
Jeff
On Mon, Sep 17, 2012 at 9:09 AM, Simone Tripodi wrote:
> Salut Jeff,
>
> profiling sounds a good idea but I didn't understand how mvn is abl
Extremely difficult to help without seeing the error text message. At
least post that.
/Anders
On Mon, Sep 17, 2012 at 1:31 PM, TarunKhandelwal
wrote:
> Hello All,
>
> I am implementing Maven for the build Automation and as well as Test Run.
> Now i have two different projects and i have created
Hello All,
I am implementing Maven for the build Automation and as well as Test Run.
Now i have two different projects and i have created one Parent Project to
build both of them.
But now some error is coming when i am running parent pom.xml.
Its Building only single Module.
And after running Test
On Mon, Sep 17, 2012 at 5:26 PM, Kristian Rosenvold
wrote:
> You should probably be looking into parallelizing your tests :) .
Or looking at what your tests are doing.
32 minutes sounds like you are doing integration type testing and not
unit tests.
Pull the integration tests into their own modu
Hi,
It seems to be impossible to have multiple execution configuration for
direct cli plugin invocation.
So i refactored plugin that now it can invoke directly from cli with
multiple configurations.
Markku
On 09/17/2012 11:30 AM, Markku Saarela wrote:
Hi,
I have problem with plugin devel
Hi,
I have problem with plugin developed by myself.
I have just figured out that the problem is with executionIds when
running from command line.
It get default-cli as execution id and not found configuration from
other execution id.
I just try to figure out how you can have different exec
Sorry Markku, but I'm not sure I understand what you want. You have a
problem using a plugin you developed?
The best thing is to post at least an excerpt of that POM part, the
problematic one, so that we can have a look.
Even better would be having a test project posted somewhere.
Cheers
2012/9/
You should probably be looking into parallelizing your tests :) .
Either through using the parallel attribute of surefire or or
forkMode=perThread.
( see http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html)
forkMode=perThread is probably the easiest to get going with, but the
pa
Hi,
I made Maven plugin and it's parameter configuration is working plugin
element but notin execution elements. Maven reports parameters are
missing or invalid.
So how to get execution configuration working?
rgds,
Markku
Hi Simone,
Simone Tripodi wrote:
> Salut Jeff,
>
> profiling sounds a good idea but I didn't understand how mvn is able
> to resolve profiled dependencies, I mean, in my project X I need to
> import the c.jar dependency with mac-x86_64 as classifier - how to
> guarantee transitive dependencies a
Salut Jeff,
profiling sounds a good idea but I didn't understand how mvn is able
to resolve profiled dependencies, I mean, in my project X I need to
import the c.jar dependency with mac-x86_64 as classifier - how to
guarantee transitive dependencies are imported for the same platform
(same classif
23 matches
Mail list logo
