Thanks Justin.
Now we just have to pass the hat around to buy the coverage crew a mac :)
Michael
On 22 July 2011 15:04, Justin Deoliveira jdeol...@opengeo.org wrote:
I can confirm, I get the same error when I try to build that module.
Hey that got me just now as well! Can we disable tests for it as a temporary
measure ...
--
Jody Garnett
On Friday, 22 July 2011 at 4:14 PM, Michael Bedward wrote:
Thanks Justin.
Now we just have to pass the hat around to buy the coverage crew a mac :)
Michael
On 22 July 2011
Ciao Guys,
you can go ahead and disable the tests. As soon as I will have time
I will look into it again. Not having a mac, does not help though.
Regards,
Simone Giannecchini
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder
Via Poggio
Here is a temp fix… add the following to coveragetools/pom.xml
profiles
profile
activation
os
familymac/family
/os
/activation
properties
skipTeststrue/skipTests
/properties
/profile
/profiles
Do you want me to commit this so we can get back to work?
--
Jody Garnett
On Friday, 22 July
On Fri, Jul 22, 2011 at 10:36 AM, Jody Garnett jody.garn...@gmail.com wrote:
Here is a temp fix… add the following to coveragetools/pom.xml
profiles
profile
activation
os
familymac/family
/os
/activation
properties
It is a bit extreme; I should be able to specify a pattern; need an example.
This was just enough to get me back to development.
I have committed a better fix with a profile that just turns off that one test
(on mac only).
--
Jody Garnett
On Friday, 22 July 2011 at 6:59 PM, Andrea Aime
Jody, a better way to exclude a single test in a child project (rather than
copy the entire surefire plugin config, which is about 40 lines long) is to
use the test.exclude.pattern property. That is what is there for :)
profile
activation
os
familymac/family
/os
thanks
--
Jody Garnett
On Friday, 22 July 2011 at 11:23 PM, Justin Deoliveira wrote:
Jody, a better way to exclude a single test in a child project (rather than
copy the entire surefire plugin config, which is about 40 lines long) is to
use the test.exclude.pattern property. That is
I can confirm, I get the same error when I try to build that module.
On Thu, Jul 21, 2011 at 10:53 PM, Michael Bedward michael.bedw...@gmail.com
wrote:
Dear mac aficionados,
Is anyone else getting a test failure when building the
unsupported/coveragetools module on trunk ? I just want to
