Niall Pemberton wrote:

> On Mon, Sep 6, 2010 at 12:16 PM, Stefan Bodewig <bode...@apache.org>
> wrote:
>> On 2010-09-06, Niall Pemberton wrote:
>>
>>> On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig <bode...@apache.org>
>>> wrote:
>>>> Hi,
>>
>>>> some time back we had a discussion that skipTest was the preferred
>>>> property to use when we want to tell mvn not to run tests - well, it
>>>> doesn't work, at least not for Cocoon 2.2.x.
>>
>>>> My theory is that those properties are interpreted by the surefire
>>>> plugin rather than mvn itself.
>>
>>> Yes, they are plugin parameters:
>>
>>> http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html
>>
>> Thank you for the confirmation.
>>
>>> And from the docs the skipTests parameter was added in version 2.4 of
>>> the surefire plugin
>>
>>> [...] and cocoon is using version 2.3 of the surefire plugin (see
>>> pluginManagement section of the pom):
>>
>>> skipTests was introduced to replace the more verbose
>>> "maven.test.skip=true" - you could use that instead though.
>>
>> Is there a difference between maven.test.skip and maven.test.skip.exec
>> (which we use now)?  I see there is a skip property in addition to the
>> skipTests property - the former even avoids compilation of the tests, so
>> I gues this is the difference here as well.
> 
> Yes, the "skipTests" and "maven.test.skip.exec=true" are the same -
> the tests get compiled, but not executed.  The "maven.test.skip=true"
> doesn't compile or execute the tests.

And it will therefore not build attached tests.jars which may result 
depending artifacts to fail ...

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Reply via email to