On Sat, Feb 8, 2020 at 11:40 AM Nico Kadel-Garcia <nkadel(a)gmail.com> wrote:
On Sat, Feb 8, 2020 at 10:44 AM Neal Gompa <ngompa13(a)gmail.com> wrote:
>
> On Sat, Feb 8, 2020 at 6:23 AM Ankur Sinha <sanjay.ankur(a)gmail.com> wrote:
> >
> > Hello,
> >
> > netcdf-java[1] uses the Gradle build system, and is required to update
> > hdfview[2] to the latest version. Gradle, however, was retired[3] as
> > "out of date, broken, fails to build, basically unmaintainable".
> >
> > Now, I know that following our system, one must package Gradle first but
> > given the retirement comment, packaging and then maintaining it does not
> > appear a simple task, and for one dependency only, it seems overkill.
> >
> > Is there perhaps a way of bypassing that somehow? For example, is there
> > a way to use good old Maven to build a Gradle based project?
> >
> > [1]
https://docs.unidata.ucar.edu/netcdf-java/5.2/userguide/building_from_sou...
> > [2]
https://bugzilla.redhat.com/show_bug.cgi?id=1797361
> > [3]
https://src.fedoraproject.org/rpms/gradle/blob/master/f/dead.package
> >
>
> Gradle is a blocker for a lot of projects, unfortunately. Not
> supporting what appears to be one of the preferred build tools in the
> Java ecosystem has made things quite painful...
How difficult is it to migrate a gradle build to a maven build?
Very. Gradle is script oriented. Everything is written in Groovy.
--
真実はいつも一つ!/ Always, there's only one truth!