Re: [Geotools-devel] Making Maven less verbose?

2007-06-29 Thread Andrea Aime
Martin Desruisseaux ha scritto: > Martin Desruisseaux a écrit : >> I re-enabled on trunk. I'm not try to inspect what happen with the tests. > > Typo: "I'm now trying to inspect..." Cory committed changes on the failing test yesterday (and on the tested class too). Cheers Andrea --

Re: [Geotools-devel] Making Maven less verbose?

2007-06-29 Thread Martin Desruisseaux
Martin Desruisseaux a écrit : > I re-enabled on trunk. I'm not try to inspect what happen with the tests. Typo: "I'm now trying to inspect..." - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE

Re: [Geotools-devel] Making Maven less verbose?

2007-06-29 Thread Martin Desruisseaux
Andrea Aime a écrit : > But it's not, and if a module has lots of tests (like the Metadata > module that is failing now) it's hard to spot what's happening > by inspection of each single surefire report. > > Re-enabling summary I get: > Running org.geotools.util.ObjectCacheEntryTest > Tests run:

Re: [Geotools-devel] Making Maven less verbose?

2007-06-29 Thread Andrea Aime
Cory Horner ha scritto: > Martin Desruisseaux wrote: >> Just realized that Maven documentation said "just print the test cases that >> has >> errors", but in practice Maven doesn't prints any test at all, even in case >> in >> error. >> >> Will wait in the hope that this is a Maven bug to be fi

Re: [Geotools-devel] Making Maven less verbose?

2007-06-28 Thread Martin Desruisseaux
Cory Horner a écrit : > I like the change, but would like to easily be able to set a flag to > have full output (-Dtests.verbose=true). Right now the build boxes tell > us that the build is broken, but not which test failed. I also cannot > figure out which test failed from the command line (b

Re: [Geotools-devel] Making Maven less verbose?

2007-06-28 Thread Cory Horner
Martin Desruisseaux wrote: > Just realized that Maven documentation said "just print the test cases that > has > errors", but in practice Maven doesn't prints any test at all, even in case > in > error. > > Will wait in the hope that this is a Maven bug to be fixed in the future, > unless >

Re: [Geotools-devel] Making Maven less verbose?

2007-06-28 Thread Martin Desruisseaux
Just realized that Maven documentation said "just print the test cases that has errors", but in practice Maven doesn't prints any test at all, even in case in error. Will wait in the hope that this is a Maven bug to be fixed in the future, unless peoples wish to roll back this change. In the m

Re: [Geotools-devel] Making Maven less verbose?

2007-06-27 Thread Justin Deoliveira
+1, it will make the continuum logs smaller and easier to read. -Justin Martin Desruisseaux wrote: > I'm in the process of deploying GeoAPI milestone and updating Geotools code > for > the removal of deprecated methods in BoundingBox and renaming of > PointArray.getPosition(...) to getDirectPo

Re: [Geotools-devel] Making Maven less verbose?

2007-06-27 Thread Jody Garnett
That sounds great Martin :-) > I'm in the process of deploying GeoAPI milestone and updating Geotools code > for > the removal of deprecated methods in BoundingBox and renaming of > PointArray.getPosition(...) to getDirectPosition(...). > > For making the process easier, I tuned the following op

[Geotools-devel] Making Maven less verbose?

2007-06-27 Thread Martin Desruisseaux
I'm in the process of deploying GeoAPI milestone and updating Geotools code for the removal of deprecated methods in BoundingBox and renaming of PointArray.getPosition(...) to getDirectPosition(...). For making the process easier, I tuned the following option to "false". Is there any objection