OreoC wrote:
>
> Thus, I just do:
> gradle copyRuntimeDependencies
>
That works. I tweaked it a bit since I have a slightly deviating build dir
("build" is already used by the existing ant script):
into(project.buildDirName + '/output/lib')
Thank you very much!
...
What worries me is that I would not have come up with this solution in any
way. I've been poking at Gradle for a number of days now and even though
things are working now (thanks to some great support here), and I understand
creation and configuration of tasks, I'm still not comfortable with the
overall environment. I would not even have envisioned a solution in this
line.
Maven took me quite some reading to get my head around, and I still don't
have the details of the references clear, but that is caused because we
haven't really start using it and probably will come with some experience.
Ant and Ivy were simple. But Gradle is complex as well, and I can't put my
finger on the "where"... Like Maven, the internals of the engine, the
administration, are not insightful.
So I'm not sure I want to go here. If it takes me this long te grasp it, I
will never be able to explain or defend this as a build environment to my
colleague's; ANT build script are understood almost without explanation, but
Gradle scripts are not...
Maybe ANT + Ivy are a better suite, using the ANT Groovy task to prevent
strange tasks. Or just ant with Maven tasks. Or Groovy with AntBuilder. Or
GANT. Pfffft... I don't know. I need to reevaluate.
--
View this message in context:
http://old.nabble.com/best-way-to-gather-the-libraries-tp26966955p26972083.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
