Notes on Reading Gradle Release Notes Since Version 1.5

[殷啟聰]

Hi Komal,

Actually, Gradle is able to download missing plugins if and only if
there are repositories closure declared inside buildscript closures.
For example:

buildscript {
  repositories {
    mavenCentral()
  }
  dependencies {
    classpath "org.gradle.jacoco:gradle-jacoco:2.4"
}

Although we can patch the build scripts during the packaging, in
reality no project will write this because jacoco is a built-in
plugin.

So we should rethink about that :) . Anyway, I have set up my GitHub
repo (http://github.com/seamlik/debianpkg-gradle) for packaging
Gradle, Groovy 2 and so on. Currently I think we can first update
Gradle to 1.12, then to 2.4.

Cheers,
Kai-Chung


2015-05-21 16:08 GMT+08:00 Komal Sukhani <komaldsukhani at gmail.com>:
> Hi,
>
> Thank you Kai-Chung.
>
> I was about to mail you today itself. I have rechecked release notes list
> that
> you have added on wiki and it covers everything.
>
> Next, I was planning to read the logs of Debian gradle package to find out
> how
> the package was built. But as you rightly said packaging of missing
> dependency
> is must, I will focus on packaging of PMD as you are focusing on JaCoCo.
>
> Komal Sukhani.



-- 
/*
* 殷啟聰 | Kai-Chung Yan
* Full-time student of Providence University of Taiwan
* LinkedIn: <https://linkedin.com/in/seamlik>
* Blog: <seamlik.logdown.com>
*/