Paul de Vrieze

This is a feature I would also really want. As a workaround it is possible to have a solution repo (with all code) and a problem repo (with only the...

These are on the list. I figured I'd keep the old ones around a while to allow people more time to move. I can make the deprecations errors though.

I've reviewed these functions. All of them should be properly deprecated. At the same time I have moved the error level to `ERROR` for some that are quite old now....

I haven't really tried looking at jdk versions after 8 (including java 9 modules). I'll have a look at trying to reorganize the packages to remove package name sharing.

One of the issues is that there is not really a good path to (jigsaw) modular with multiplatform Kotlin. I may come up with a hack that will do so...

The current head should not have any issues with modular package names anymore. I will wait until kotlin 1.3.40 to make a proper modular version as that version has `withJava`...

This should be resolved with the 0.11.1.1 release. In addition there is the jigsaw branch that should be properly modular, but may create all kinds of issues due to having...

A `@DynamicSerialName` feature basically conflicts with the transparent list support, unless it was to be a built-in filtering system similar to what the example code provides. I'll keep it open...

@fkrauthan Basically that is already possible. If you pass `XmlWriter` or `XmlReader` instances to the format those can be filters rather than directly directed to a reader/writer.

Interesting one. Clearly not in the "philosophy" of XML. The use of "value" like attributes isn't really intended, and just using element content itself is possible. Another one is that...