On Tue, 23 Jun 2020, Olek Wojnar wrote:
> If you insist on using Gradle, I think that you should package the Google
> plugin separately.
Agreed.
> The names are already different so it may create some confusion (the
You do know that periods are valid in Debian package names, right?
So com.goog
Hi Samyak,
On Tue, Jun 23, 2020 at 5:56 PM Samyak Jain 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 i
Oops, meant to send to list...
-- Forwarded message -
From: Olek Wojnar
Date: Tue, Jun 23, 2020 at 12:20 PM
Subject: Re: [Help] gradle-plugin-protobuf
To: Samyak Jain
Hi Samyak,
On Tue, Jun 23, 2020 at 8:12 AM Samyak Jain wrote:
> While parsing through dependencies
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
> w
Hi Samyak,
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
Hey,
The package gradle-plugin-protobuf exists in Java-Team and hasn't been
updated in the past few years [1].
While parsing through dependencies for bundletools. Yesterday, on reviewing
through the same I found a problem which is creating the conflict. The
problem is that the upstream source pac
6 matches
Mail list logo
