Radai Rosenblatt

i have a slightly less ugly (i hope) workaround: ```java private static Arguments parse(String[] cmdLine) { Arguments result = new Arguments(); CmdLineParser parser = new CmdLineParser(result); try { parser.parseArgument(cmdLine); }...

@mlevison - maintenance and usability nightmare, let me explain: suppose i have a multi-module project. every module has "layered" test cases - starting at crud tests, then inter-class integration, then...

anything can be abused. I dont think something potentially being abused is reason not to include it. dependencies are not really a scenario: 1. they are meant to describe completely...

loose groups (tags) and the ability to specify high level layers of tests as you describe would suit my purpose very well. it would allow the low layers to run...

ended up finding a few bad schemas in other unit tests as well ...

updated the PR to allow dangling content when parsing from InputStream

i'll add a check for the File method. as for the case of a buffer full of whitespace (and presumably content beyond that) - I'm ok with missing that validation...

that was an excellent catch @KalleOlaviNiemitalo. i've added a test for File input and adapted the code to work for all cases of dangling input. except for the case of...

@RyanSkraba - any chance of this making it in ?

Hey folks. I'd like to elaborate a little here about why the avro-util project exists. we can then see if involving upstream avro makes sense in anything. TL;DR - when...