Hello,
You can have a look at the generated report xml files in target/invoker-reports/
Those files will give minimals informations (status of the it test and
time spend on running it)
HTH,
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Hi,
We have a standard maven multi module layout, like this :
project
- - -project-external-api (1.2.1-SNAPSHOT) - contains wsdl and stubs of
external client needed by the project
- - -project-core (1.2.1-SNAPSHOT) - core of the project
- - -project-ws (1.2.1-SNAPSHOT) - webapp of the project
-
Hi all,
and sorry for the long post; what I want to acieve is a bit complex:
I am currently integration-testing a tool that allows one to perform a
variety of bytecode instrumentation tasks (for profiling/JVM research).
Said tool consists of two components: a server running in a separate JVM
Hi,
Max Carpentier wrote
We would like to make a new release of the project, but there's a problem
: project-external-api and and project-ws-api haven't changed since the
last release...
what should we do ?
Very short answer: So what? Just make the release and it's done.
Is it a
General practice I follow is...group modules in your multi-module project
that you do want to version as a group, move things that don't need to be
versions as often (or more often) to a separate project and add as
dependency.
-Dave
On Fri, Dec 9, 2011 at 6:27 AM, Max Carpentier
Hi,
The Mojo team is pleased to announce the release of the Mock
Repository Manager version 1.0-alpha-1.
The Mock Repository Manager suite of projects are used to provide mock
or lightweight Maven Repository Managers for use during integration
testing of Maven plugins.
http://mojo.codehaus.org/mrm
Interesting post; you suggest that the surefire-providers should have
extensive freedoms in terms of controlling details of the fork, I
like that suggestion a lot, it's a very good extension of the current
provider api.
I'll give you some pointers into the code on this;
The
