On Tue, 2019-02-26 at 12:40 +0100, Emmanuel Bourg wrote:
> Le 26/02/2019 à 12:22, Sjoerd Simons a écrit :
>
> > ASM7 mode seems to have been introduced in the gradle v5.x series.
> > Not
> > sure if it makes sense for buster to upgrade to that (I really
> > don't
> > know much about java, so no id
Le 26/02/2019 à 12:22, Sjoerd Simons a écrit :
> ASM7 mode seems to have been introduced in the gradle v5.x series. Not
> sure if it makes sense for buster to upgrade to that (I really don't
> know much about java, so no idea about the impact)?
We can't upgrade to Gradle 5 unfortunately, not unti
On Tue, 2019-02-26 at 11:35 +0100, Emmanuel Bourg wrote:
> Le 26/02/2019 à 10:20, Sjoerd Simons a écrit :
>
> > I've atteched the output of running docker build on the DockerFile
> > i
> > attached to reproduce the issue; The relevant part in the gradle
> > build
> > seems to be:
>
> Thank you! T
Le 26/02/2019 à 10:20, Sjoerd Simons a écrit :
> I've atteched the output of running docker build on the DockerFile i
> attached to reproduce the issue; The relevant part in the gradle build
> seems to be:
Thank you! The "Malformed jar" message is just a warning. The actual
issue is:
> Caused by
On Mon, 2019-02-25 at 23:59 +0100, Emmanuel Bourg wrote:
> Thank you for the report Sjoerd. What error did you get when
> compiling
> gradle with the rebuilt bsh?
>
> Emmanuel Bourg
Btw; I tested with forcing bsh to build with openjdk-8 instead and then
the issue doesn't occur while building grad
Thank you for the report Sjoerd. What error did you get when compiling
gradle with the rebuilt bsh?
Emmanuel Bourg
Source: bsh
Version: 2.0b4-19
Severity: serious
When building bsh with openjdk-11 it seems that afterwards building packages
using it fails e.g. after rebuilding bsh gradle fails to build.
Attached is a dockerfile which nicely shows the issue
-- System Information:
Debian Release: buster/sid
A
7 matches
Mail list logo
