Hi,
you have probably noticed the 2.0.x nightly builds are failing.
They are failing because of a supposedly missing method, that
is actually there... but then, it is not for the compiler
Odd uh?
Took me a while but I tracked it down and would like to share
the solution for posterity.
The compiler complains that SVGGraphicsFactory.resetCache is not
there, but if you look in the gt2 sources, it's there.
That class has a history though: in the beginning, and until
a few months ago, it was part of gt-render, and was then
moved to its own module, gt-svg, because of the heavy dependencies
it carries (Batik).
Now, what happens is that the jars deployed on repo.opengeo.org
by the nightly builds still contain the old class, which happens
to be in the compiler classpath before the new one, which results
in the failure to build.
How is that possible? The nightly builds of GeoTools are
not clean builds, meaning the old .class files are still there
in target/class even if the sources are not there, and they
are packaged in the jar as a result. Resulting in phantom class
(or phantom method) build failures.
I've just modified the 2.6.x nightly build to make clean during
the build, it will be slower, but will build the right jars 
(the other nightly builds had the clean step already)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.