Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Samyak Jain <samyak.jn11@gmail.com>
Newsgroups: linux.debian.maint.java
Subject: Re: [Help] gradle-plugin-protobuf
Date: Tue, 23 Jun 2020 19:00:03 +0200
Message-ID: <AkUr9-wd-29@gated-at.bofh.it>
References: <AkQ49-6wi-3@gated-at.bofh.it> <AkQdP-6zw-5@gated-at.bofh.it>
Old-Return-Path: <samyak.jn11@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="00000000000016f77305a8c33ceb"
Approved: robomod@news.nic.it
Lines: 64
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:11722

--00000000000016f77305a8c33ceb
Content-Type: text/plain; charset="UTF-8"

Hi Sudip.


gradle-plugin-protobuf is being used by libspring-java, so if you are
> updating gradle-plugin-protobuf you will need to patch libspring-java
> to use the new gradle-plugin-protobuf. And also the Debian version is
> 0.9.2-1, but the new google protobuf-gradle-plugin is 0.8.12 so you
> will need to add Epoch to the version.
> imho, it will be much easier to patch 'bundletool' to use
> ws.antonov.gradle.plugins:gradle-plugin-protobuf.
>

Thanks for the heads-up, I'll see if bundletool can be tweaked accordingly.
Since there is a lot amount of changes with all the changes in the tag.
Isn't it
feasible to package it from scratch if we are doing it? It's just a
thought, as Olek suggested
by packaging it to a new repo won't cause conflict to the old dependent
package. (Thanks for the suggestions).

I'll see for the most feasible way, but in the long run, we need to switch
to the newer
gradle-plugin-protobuf, isn't it?

Thanks and regards
Samyak Jain
(samyak-jn[m])

--00000000000016f77305a8c33ceb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Sudip.<br></div><div><br></div><div><b=
r></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
gradle-plugin-protobuf is being used by libspring-java, so if you are<br>
updating gradle-plugin-protobuf you will need to patch libspring-java<br>
to use the new gradle-plugin-protobuf. And also the Debian version is<br>
0.9.2-1, but the new google protobuf-gradle-plugin is 0.8.12 so you<br>
will need to add Epoch to the version.<br>
imho, it will be much easier to patch &#39;bundletool&#39; to use<br>
ws.antonov.gradle.plugins:gradle-plugin-protobuf.<br></blockquote><div><br>=
</div><div><span style=3D"font-family:monospace">Thanks for the heads-up, I=
&#39;ll see if bundletool can be tweaked accordingly.</span></div><div><spa=
n style=3D"font-family:monospace">Since there is a lot amount of changes wi=
th all the changes in the tag. Isn&#39;t it</span></div><div><span style=3D=
"font-family:monospace">feasible to package it from scratch if we are doing=
 it? It&#39;s just a thought, as Olek suggested</span></div><div><span styl=
e=3D"font-family:monospace">by packaging it to a new repo won&#39;t cause c=
onflict to the old dependent package. (Thanks for the suggestions).</span><=
/div><div><span style=3D"font-family:monospace"><br></span></div><div><span=
 style=3D"font-family:monospace">I&#39;ll see for the most feasible way, bu=
t in the long run, we need to switch to the newer <br>gradle-plugin-protobu=
f, isn&#39;t it?</span></div><div><span style=3D"font-family:monospace"><br=
></span></div><div><span style=3D"font-family:monospace">Thanks and regards=
</span></div><div><span style=3D"font-family:monospace">Samyak Jain</span><=
/div><div><span style=3D"font-family:monospace">(samyak-jn[m])</span><br></=
div></div></div>

--00000000000016f77305a8c33ceb--