I'm currently running an old version (0.17) of Boofcv and want to upgrade. The documentation (https://boofcv.org/index.php?title=Download ) is confusing:
The easiest way to use boofcv is to reference its jars on Maven Central. See below for Maven and Gradle code. BoofCV is broken up into many modules. To make it easier to use BoofCV all of its core functionality can be referenced using the 'all' module. Individual modules in "integration" still must be referenced individually.
Artifact List
boofcv-core : All the core functionality of BoofCV boofcv-all : All the core and integration packages in BoofCV. YOU PROBABLY WANT CORE AND NOT THIS
This is self-contradictory - do we use "all" or "core"?
When I introduce 0.32 version of boofcv-core I get many unresolved references, such as Description Resource Path Location Type ImageFloat32 cannot be resolved to a type BoofCVTest.java
Three parts of my question: Have the fundamental types for images been renamed? How will legacy code need editing? What is the default set of libraries in Maven?
There's been a lot of refactoring since 0.17 because of how verbose things were getting and to simplify the API. For example, ImageFloat32 is now GrayF32. The easiest way to figure out all the changes is to look at the relevant example code.
For modules, start with boofcv-core. Then add modules listed in integration as needed. For example if you need android support add boofcv-android. If you include boofcv-all you will have a lot of stuff you probably don't need, like Kinect support.