On 08/08/2008, at 9:55 PM, Vincent Siveton wrote:
2008/8/7 Arnaud HERITIER <[EMAIL PROTECTED]>:
Hi all,
You noticed that we changed in plugins the behavior of ITs.
We would like to have your advice :
Do you want to have ITs activated by default in the plugin build ?
I think we need to separate your question between core and plugins:
* for core +1 to *disabled* ITs by default
* for plugins +1 to *activated* ITs by default with maven.test.skip
(first choice) or a dev property in the settings (second choice).
Why ?
I know it could be time consuming but when developing/deploying
something, we need to be sure that CI will be happy. To increase our
chances, running ITs by default ie as part of the lifecycle is the
only way I can see.
I think the slowness will turn people towards continually wanting to
skip them rather than run them. It's an interesting question of what
impression it gives to the contributors - impressed by the testing, or
annoyed by the speed of the build?
Just some stats: actually on 38 plugins, around 13 have ITs.
This is probably more to do with lack or limitation of framework at
the time the plugins were written - those that have had active
development recently have acquired the tests.
Hopefully the work you guys are doing to have a standard rig will
encourage this further!
My 2c :)
- Brett
Cheers,
Vincent
--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
