Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Roger Shimizu <rogershimizu@gmail.com>
Newsgroups: linux.debian.maint.java
Subject: Re: Packaging issue on gradle's library dependency
Date: Mon, 21 Dec 2015 15:40:02 +0100
Message-ID: <qI9N0-7Fe-13@gated-at.bofh.it>
References: <qHsf0-5oW-15@gated-at.bofh.it> <qHtuq-66C-11@gated-at.bofh.it>
Old-Return-Path: <rogershimizu@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 77
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:8682

On Sun, Dec 20, 2015 at 2:28 AM, =E6=AE=B7=E5=95=9F=E8=81=B0 <seamlikok@gma=
il.com> wrote:
> I haven't dug too much about your package, but I think you are right
> about Proguard missing the POM files. Currently "proguard" does not
> generate maven-repo data which are POMs stored in
> /usr/share/maven-repo. It will be great to submit a wishlist bug to
> src:proguard, but if you want to get your package prepared soon you
> can avoid using gradle-debian-helper (--buildsystem=3Dgradle) by
> directly invoking Gradle in your debian/rules. But you need to do some
> extra work:

Thanks for your reply in detail!
For the lack of POMs for proguard, it seems fine since you introduced
me the workaround.

> # 1. Invoking Gradle
>
> See <http://anonscm.debian.org/cgit/pkg-java/bintray-client-java.git/tree=
/debian/rules?h=3Ddebian/0.8.1-1>.
> The point is you need to add "--offline --gradle-user-home
> .gradlehome" and after the invocation you need to remove .gradle and
> .gradlehome.
> # 2. Patch build scripts
>
> Replace all repository closures with:
>
> repositories {
>   flatDir { dirs '/usr/share/java' }
>   maven { url 'file:///usr/share/maven-repo' }
> }

I have no experienced in java related packaging, so I didn't get what
you said at first.
But I found a patch to migrate from the way you proposed to what I
have been used:
- http://lists.alioth.debian.org/pipermail/pkg-java-commits/2015-October/04=
6387.html

What I need is actually "reverse" version of above patch. (of course
with a few changes)
Now I have overcome the "proguard" library issue.

However, I met new dependency issue, log as below.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
Evaluating project ':smali' using build file
'/home/roger/smali/smali/build.gradle'.
Compiling build file '/home/roger/smali/smali/build.gradle' using
SubsetScriptTransformer.

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':smali'.
> Could not resolve all dependencies for configuration ':smali:classpath'.
   > Could not find co.tomlee.gradle.plugins:gradle-jflex-plugin:0.0.2.
     Searched in the following locations:
         file:/usr/share/java/gradle-jflex-plugin-0.0.2.jar
         file:/usr/share/java/gradle-jflex-plugin.jar
         file:/usr/share/maven-repo/co/tomlee/gradle/plugins/gradle-jflex-p=
lugin/0.0.2/gradle-jflex-plugin-0.0.2.pom
         file:/usr/share/maven-repo/co/tomlee/gradle/plugins/gradle-jflex-p=
lugin/0.0.2/gradle-jflex-plugin-0.0.2.jar
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D

I find a few "grandle plugins" in pkg libgradle-plugins-java, which is
produced by src:gradle.
But gradle-jflex is not covered by libgradle-plugins-java, so I guess
I need to package it myself.
The upstream is:
-  https://github.com/thomaslee/gradle-jflex-plugin

I just want to confirm my understanding is correct. Thank you!

Cheers,
Roger