Hopefully a 1000 projects don't need to be updated from Gradle 4 to
Gradle 7!
> Debian does not do out-of-git builds (.git directory is removed from
> sources prior to build), thus I guess this plugin would not be of much
> use (but I may be wrong).
>
Still required since it creates a BoofVers
Instead of updating the "gradle" command could we just install a new
"gradle7" command that points to Gradle 7 instead? I don't think Gradle is
very backwards compatible so that might be the easiest solution.
For Jars that BoofCV downloads, It doesn't download anything outside of
Gradle. It uses a
Based on Dima's comments. Is there any reason we can't just use the Gradle
Wrapper? That way each project can use the version of Gradle it works with
instead of single version for all projects. The only reason I see to not
use Gradle wrapper is because it will download its dependencies and maybe
fo
Hi Andrius,
Good to meet you and thanks for the first attempt at getting BoofCV in
Debian. To keep things simple, that approach that I'm thinking of is to add
"libboofcv-core" to Debian first, which has all the core functionality and
can be added to a project now by referencing "boofcv-core" modul
4 matches
Mail list logo
