test dependency in war goal

["March, Andres" <am...@soe.sony.com>]

I have read the archive about people who wanted to bypass tests in
certain goals like war.  I was wondering what came of this.  I don't
exactly want to bypass them but I would like to set a test.failonerror
property = false when running war.  I believe in always testing but this
inflexibility (if it still exists) goes too far.  When many people are
developing software, one person should not impede the progress of others
just because one of their tests fail that has no affect on the parts of
the application others are working on.  Unit tests are not the end of
testing, just the beginning.  Building and testing a distributable still
adds value to the development process even if parts of the app are
broken (as defined by their unit tests).

 

I have read comments that suggest we should just override these goals
but this eliminates the benefit of the plugin altogether.  If this is
such a highly requested feature, it should be added.  I would be more
than willing if I knew it would be accepted by the plugin maintainers.
Of course this would be an option turned off by default.

 

-----------------------------------------

Andres March

Platform - Apps Engineering

Sony Online Entertainment

desk: 858.577.3373

cell:   619.519.1519

 

RE: test dependency in war goal

[Matt Read <mr...@spotd.co.uk>]

How about:

maven.test.failure.ignore=true

?
 

> -----Original Message-----
> From: March, Andres [mailto:amarch@soe.sony.com] 
> Sent: 28 July 2004 17:30
> To: Maven Users List
> Subject: test dependency in war goal
> 
> I have read the archive about people who wanted to bypass 
> tests in certain goals like war.  I was wondering what came 
> of this.  I don't exactly want to bypass them but I would 
> like to set a test.failonerror property = false when running 
> war.  I believe in always testing but this inflexibility (if 
> it still exists) goes too far.  When many people are 
> developing software, one person should not impede the 
> progress of others just because one of their tests fail that 
> has no affect on the parts of the application others are 
> working on.  Unit tests are not the end of testing, just the 
> beginning.  Building and testing a distributable still adds 
> value to the development process even if parts of the app are 
> broken (as defined by their unit tests).
> 
>  
> 
> I have read comments that suggest we should just override 
> these goals but this eliminates the benefit of the plugin 
> altogether.  If this is such a highly requested feature, it 
> should be added.  I would be more than willing if I knew it 
> would be accepted by the plugin maintainers.
> Of course this would be an option turned off by default.
> 
>  
> 
> -----------------------------------------
> 
> Andres March
> 
> Platform - Apps Engineering
> 
> Sony Online Entertainment
> 
> desk: 858.577.3373
> 
> cell:   619.519.1519
> 
>  
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org