maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <>
Subject Re: How can I force a Maven task to depend on other Maven tasks?
Date Thu, 31 Oct 2013 15:34:49 GMT
No such thing as a Maven task.
Maven projects produce artifacts which other projects can declare as 
You can have Maven projects that include sub-projects (multi-module 

Can you rephrase your question or describe what you are trying to do.

Bear in mind that Maven is used by tens of thousands of software 
development projects so that if you can describe what you want to do, 
someone will have already done it and can show you how.


On 31/10/2013 11:05 AM, Russell Gold wrote:
> ‘mvn test’ should compile any code that needs to be compiled. It sounds as though
you might have intermittent tests. Can you show us a log of such a test run followed by a
“compile test” run?
> - Russ
> On Oct 31, 2013, at 11:00 AM, Andrew Pennebaker <> wrote:
>> When I run `mvn test`, I sometimes get misleading reports ("all unit tests
>> pass"), when in fact, upon manually recompiling the code with `mvn compile`
>> and running `mvn test` again, the new code shows test failures.
>> Is this normal behavior for a Maven project? How can I force a Maven task
>> to depend on other Maven tasks?
>> -- 
>> Cheers,
>> Andrew Pennebaker
> -----------------
> Author, Getting Started with Apache Maven <>
> Come read my webnovel, Take a Lemon <>,
> and listen to the Misfile radio play <>!

Ron Wheeler
Artifact Software Inc
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message