On 2010-09-06, Jörg Schaible wrote:
> Niall Pemberton wrote:
>> 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.j
Niall Pemberton wrote:
> On Mon, Sep 6, 2010 at 12:16 PM, Stefan Bodewig
> wrote:
>> On 2010-09-06, Niall Pemberton wrote:
>>
>>> On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig
>>> wrote:
Hi,
>>
some time back we had a discussion that skipTest was the preferred
property to use whe
On Mon, Sep 6, 2010 at 12:16 PM, Stefan Bodewig wrote:
> On 2010-09-06, Niall Pemberton wrote:
>
>> On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig 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
On 2010-09-06, Niall Pemberton wrote:
> On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig 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.
>> M
On Mon, Sep 6, 2010 at 5:03 AM, Stefan Bodewig 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 interp
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. Unlike the ve
