On 23.04.2021 16:17, Emma Atkinson wrote:
Christoph
The guide suggests Ant and Gradle builds coexist until one has
confidence that both build tools produce the same things.
That was what I intended and why I choose the Gradle-path, but I could
not make it work. A tool doing the heavy lifting
While Ivy is an excellent tool to manage dependencies. It has a niche
market. So unless somebody steps for it and implements a better support
for that, I fear voting for it won't do that much.
On 4/23/21 9:27 AM, Oliver Rettig wrote:
+1 for better ivy integration
> On 23.04.2021 15:22,
+1 for better ivy integration
> On 23.04.2021 15:22, Laszlo Kishalmi wrote:
> > Ant projects can be fairly simply can be migrated to Gradle. It can
> > support your current folder structure. Your file/directory based library
> > dependencies, and occasional customization you made.
>
> Been there,
Christoph
It so happens I have just read a migration guide that looks reasonable and
do-able. It's at
https://docs.gradle.org/current/userguide/migrating_from_ant.html
and addresses option for Ant and mentions Ivy.
The guide suggests Ant and Gradle builds coexist until one has confidence
that
On 23.04.2021 15:22, Laszlo Kishalmi wrote:
Ant projects can be fairly simply can be migrated to Gradle. It can
support your current folder structure. Your file/directory based library
dependencies, and occasional customization you made.
Been there, tried that, and failed.
If you have a
On Fri, 23 Apr 2021 at 15:23, Laszlo Kishalmi wrote:
> Ant projects can be fairly simply can be migrated to Gradle.
Well, I've often said Gradle is just Ant with slightly better syntax! :-)
Joking aside, good point, and I'd be interested to see a converter too.
Best wishes,
Neil
If someone has a well establised Ant project and he would migrate that
to Maven, then he/she is looking at the wrong direction.
Ant projects can be fairly simply can be migrated to Gradle. It can
support your current folder structure. Your file/directory based library
dependencies, and
