+1, this makes more sense
Jacques
From: Paul Foxworthy p...@cohsoft.com.au
If we do have two tasks, how about
run-tests
which would revert to the older style without cobertura and would not
depend on an Internet connection, and
run-tests-with-coverage
which would use cobertura and would
Le 25/03/2011 09:12, Jacques Le Roux a écrit :
+1, this makes more sense
Jacques
From: Paul Foxworthy p...@cohsoft.com.au
If we do have two tasks, how about
OK, as many of you are in favour of adding a new task, I will work on it.
Cheers,
--
Erwan de FERRIERES
www.nereide.biz
I have nothing against (as it can be easily bypasssed) it but it's worth to be noted that run-tests depends now on
download-cobertura, which itself depends on an internet connection. Hence run-tests can't be used on a server w/out Internet
connection
Jacques
on a server w/out Internet connection
Jacques
connection. Hence run-tests can't
be used on a server w/out Internet connection
Jacques
Hi Ruth,
it's really easy to bypass, just remove the download-cobertura call.
target name=run-tests depends=download-cobertura, build
I have been added this as there was an error in the logs when lauching
tests
be used on a server w/out Internet connection
Jacques
Hi Ruth,
it's really easy to bypass, just remove the download-cobertura call.
target name=run-tests depends=download-cobertura, build
I have been added this as there was an error in the logs when lauching
tests and the lib wasn't found
on a server
w/out Internet connection
Jacques
smime.p7s
Description: S/MIME cryptographic signature
If we do have two tasks, how about
run-tests
which would revert to the older style without cobertura and would not
depend on an Internet connection, and
run-tests-with-coverage
which would use cobertura and would have the dependency?
Better to say what tasks do and what they are, rather than
