On Fri, 17 Jan 2020 at 09:17, Driesprong, Fokko <fo...@driesprong.frl>
wrote:

> Hi Roger,
>
> We also have Java11 in our CI, but it might be that there are still some
> issues with it. I haven't battletested Avro with Java 11 at least. For
> skipping the tests, you can provide a flag to Maven:
>
> # Make sure that you're in the Java project
> cd lang/java/
> mvn clean install -DskipTests
>
> Let me know if this works for you.
>

I think it got further, but still no cigar.
https://gist.github.com/rogpeppe/330edaaeaeb7ed6530092e73952bed0a

I shall try to work out how to build avro-tools alone - I have a suspicion
that "Apache Avro Maven Service Archetype" isn't a hard requirement for
that.

  cheers,
    rog.


> Cheers, Fokko
>
>
> Op do 16 jan. 2020 om 18:48 schreef roger peppe <rogpe...@gmail.com>:
>
>> On Thu, 16 Jan 2020 at 17:21, Ryan Skraba <r...@skraba.com> wrote:
>>
>>> Hello!  For a simple, silent log4j, I use:
>>>
>>> $ cat /tmp/log4j.properties
>>> log4j.rootLogger=off
>>>
>>
>> Apparently passing those flags has sorted my stdin/stderr issue as well
>> as suppressing the warnings. I wonder what was going on there. Thanks very
>> much!
>>
>>
>>> I didn't find anything currently in the avro-tools that uses both
>>> reader and writer schemas while deserializing data...  It should be a
>>> pretty easy feature to add as an option to the DataFileReadTool
>>> (a.k.a. tojson)!
>>>
>>> You are correct about running ./build.sh dist in the java directory --
>>> it fails with JDK 11 (likely fixable:
>>> https://issues.apache.org/jira/browse/MJAVADOC-562).
>>>
>>> You should probably do a simple mvn clean install instead and find the
>>> jar in lang/java/tools/target/avro-tools-1.10.0-SNAPSHOT.jar.  That
>>> should work with JDK11 without any problem (well-tested in the build).
>>>
>>
>> I tried that (I ran it in the lang/java directory) and I still get a
>> failure:
>> https://gist.github.com/rogpeppe/e7f199c6fefb9c05eedad9e9841de14f
>>
>> Maybe there's a way to build without running the tests, perhaps? Please
>> pardon my ignorance here.
>>
>>   cheers,
>>
>

Reply via email to