So now that both fixes are in ... here is what I should of done differently: - the moment I could not build (because of the Maven 2.0.5 requirement) I should of stopped work and sent email to the list - if I could not find Cory I should of backed out his changes
I would be interested in knowing if the build boxes are set up with Maven 2.0.4 (or if they are running Maven 2.0.5 and thus did not see the problem). Cheers, Jody > Jody Garnett wrote: >> Some success ... I have *not* hooked up the default Hints for the CRS >> utility class - the moment I do this things are back to normal. >> >> This should set off some alarm bells, basically providing Hints in >> the CRS class was the first time the GeoTools library has been hooked >> up as intended (and it did not go well). >> >> The global hints are hooked up for CommonFactoryFinder and friends >> with some deal of success. > > Ok... it seems that both myself and Jody were responsible for messing > up the build. I broke JAI by recklessly upgrading a maven plugin (it > was required for maven-2.0.6 to work well, but it totally wrecked > maven-2.0.5, etc); Jody seems to be responsible for the > Hints/Factory/CRS test failures. > > I've committed the fix for the jai problems. > > A successful build was obtained by reverting 25009, 25008, 25005, 25002. > > Cheers, > Cory. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
