Andrew Rucker Jones

No, BeanVerifier is not meant to support multiple errors in the same row. As far as the implementation goes, BeanVerifier throws an exception if anything is wrong, which interrupts the normal flow of the program. It would be difficult to make that work for multiple errors in one row. Conceptually, I decided not to provide for the case of multiple errors per row because I figured if there was one error, it might create other errors by its mere existence. I'm thinking of programming in compiled languages...

Print header separately

Nope. I went back and checked the code, or rather my javadoc, to refresh my memory. The reason an actual bean is necessary is because of the joining and splitting functionality we added a few years ago. Any fields joined on reading and split on writing are represented as a MultiValuedMap, with the exact column names in the index of the map. These names, as in the documented example, might be "Track1," "Track2," "Track3," and so on. These column names do not exist in the class. They only exist in...

Automaticaly sorting columns on HeaderColumnNameMappingStrategy

I just had a chance to read this. I had only half-understood it while scanning over the ticket early in the morning when I got up two weeks ago. I agree with Scott; this is a pretty good solution, and I can't think of a better way to do this with the built-in functionality of opencsv if you are determined to keep ordering information solely in the annotations. Well done.

CsvNumber - rounding mode

Version 5.9 has been released with this feature.

Spaces in Header and CsvBindByName.required