For anyone following the discussion: I was able to build the client by
wiping from my system everything which was left from OpenJDK-9 installation.
For some reason my previous attempt at removal did not remove JDK-9 itself
:)

And it also turned out that some "license file checker" is allergic to
having build logs stay in source directory...

Now I need to install the things I built and configure them... will post
updates when done so.

---
Thanks,
Vasily

пн, 15 окт. 2018 г. в 12:30, Vasily <[email protected]>:

> The one that comes default on Debian Stretch. "mvn --version" says 3.3.9:
>
> $ mvn --version                                            Apache Maven
> 3.3.9
> Maven home: /usr/share/maven
> Java version: 9-Debian, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-openjdk-amd64
> Default locale: ru_RU, platform encoding: UTF-8
> OS name: "linux", version: "4.15.18-1-pve", arch: "amd64", family: "unix"
>
> пн, 15 окт. 2018 г., 8:28 Mike Jumper <[email protected]>:
>
>> On Thu, Oct 11, 2018 at 11:52 AM, Mike Jumper <[email protected]> wrote:
>>
>> > On Thu, Oct 11, 2018, 11:23 Vasily <[email protected]> wrote:
>> >
>> >> I've first tried with openjdk-9-jdk, then "apt remove"d it after first
>> >> seeing this error and installed 8-jdk instead.
>> >>
>> >> What is the required version of jdk anyway?
>> >>
>> >
>> > For building master, anything from JDK 8 and later, theoretically,
>> > notwithstanding build tool bugs.
>> >
>> > The Guacamole source and build requires Java 8 as of GUACAMOLE-635,
>> which
>> > will affect the in-progress 1.0.0 release and onward. This will be
>> noted in
>> > the release notes when 1.0.0 goes out:
>> >
>> > https://issues.apache.org/jira/browse/GUACAMOLE-635
>> >
>> > It's possible that some sort of workaround will need to be put in place
>> if
>> > this affects the build even under JDK 8. This isn't happening in CI,
>> but we
>> > also don't use Debian in our CI build.
>> >
>> > For 0.9.14 and older, the build requires Java 7 or later, however the
>> > source and resulting binaries are compatible with Java 6 or higher.
>> >
>> >
>> Vasily, regarding the build failure, any idea what version of Maven you're
>> using?
>>
>> - Mike
>>
>

Reply via email to