I guess I miss something. When you generate a service engine using the archetype, tests should be enabled, as by default, it does not inherit the servicemix poms.
I have just tried creating a new service engine using the archetype and tests are not skipped ... On 9/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
gnodet wrote: > >> As tests are disabled in the archetype, I guess they are not considered >> to >> be part of "desired practices" - is this correct? > They should be enabled. But on the main tree, they are somewhat > unpredictable, use lots of ports which need to be open, do not work > if you don' t have multicast enabled, aso ... > I need to find a way to re-enable them and exclude the one that can fail > due to the environmnet. > But they *should* be enabled of course. > OK, so I will cover them in the tutorial at http://goopen.org/confluence/display/SM/Hello+World+-+SE In case the archetypes are mostly used for projects that shall have testing enabled, it makes IMHO sense to alter the archetypes. gnodet wrote: > > For the poms, I do not control them. We can not do much about that, > unless you want to fix the main maven repository. > Ah, no, thanks ;) enough other stuff to do... Georg -- View this message in context: http://www.nabble.com/Tests-are-skipped-tf2339239.html#a6525202 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
