دانلود کتاب آموزشی اندروید oreilly building and testing with gradle

دانلود کتاب آموزشی اندروید oreilly-building-and-testing-with-gradle

دانلود کتاب آموزشی برنامه نویسی اندروید

عنوان کتاب:oreilly building and testing with gradle

حجم:6 مگابایت

نویسنده:Tim Berglund and Matthew McCullough

 

 

چرا این کتاب را بخونم:

 

Ant and Maven have occupied opposing positions on the build continuum, to the
benefit and detriment of their users over the past decade. Ant chooses to offer extreme
flexibility to the user, imposing no conventions whatsoever, and not wanting to impose
any heavyweight dependency management infrastructure on the build. Apache Ivy later
added badly needed dependency management to Java builds, but still didn’t address
the lack of conventions inherent in Ant. Maven, on the other hand, offered rigid
standards and support for dependency management, but its standards were often overbearing,
and deviating from them often proved more difficult than expected.
Ant and Maven have shared considerable success in the Java marketplace, despite
important shortcomings in both tools. On the one hand, Gradle presents itself as a
sensible middle ground between both extremes, offering thoughtful conventions for
your build to follow, and making it easy for you to extend or redefine those conventions
when you want to. Gradle provides out-of-the-box build conventions and at the same
time realizes that no one set of standards can accurately reflect every build. Gradle
therefore intends to be a means of developing organization- and project-specific build
standards. It is best thought of not as a set of opinions on build standards, but as a
toolkit for developing and extending those standards with a rich, descriptive language.
Gradle also gives you options in the way it handles build dependencies. If your project’s
idiom is to declare a few top-level dependencies by name and let your build tool
determine what other libraries must be present to support your declared dependencies
(“transitive dependency management”), Gradle will let you do that, interfacing with
both Maven and Ivy repositories. If you want to download JAR files and manage
dependencies by hand in a local project directory, Gradle will not penalize you in any
way. Both approaches are first-class options. This flexibility is important in many cases,
but especially when migrating builds to Gradle: regardless of the legacy build’s opinions
on dependency management, Gradle will not oppose them.

دریافت کتاب

 

 

پسورد : www.android-learn.ir

نوشتن دیدگاه


تصویر امنیتی
تصویر امنیتی جدید

جوملا فارسی