Path: csiph.com!news.mixmin.net!aioe.org!news.servidellagleba.it!bofh.it!news.nic.it!robomod
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Newsgroups: linux.debian.maint.java
Subject: Re: [Help] gradle-plugin-protobuf
Date: Tue, 23 Jun 2020 19:50:02 +0200
Message-ID: <AkVdv-11F-11@gated-at.bofh.it>
References: <AkQ49-6wi-3@gated-at.bofh.it> <AkQdP-6zw-5@gated-at.bofh.it> <AkUr9-wd-29@gated-at.bofh.it>
Old-Return-Path: <sudipm.mukherjee@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Approved: robomod@news.nic.it
Lines: 34
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:11724

Hi Samyak,

On Tue, Jun 23, 2020 at 5:56 PM Samyak Jain <samyak.jn11@gmail.com> wrote:
>
> 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).

Yes, totally agree with Olek about creating a new package.

>
> 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?

I just had a look at upstream libspring-java and they are not using
'gradle-plugin-protobuf' with the latest versions.


-- 
Regards
Sudip