On Thu, Jun 6, 2019 at 1:51 PM Brian Goetz <brian.go...@oracle.com> wrote:
library authors suffer a familiar problem: if @Foo is meta-annotated > with a target kind of RECORD_COMPONENT, then that means it must have > been compiled against a Java 14+ JDK, which means that the resulting > classes are dependent on JDK 14+, unless they use something like MR Jars > to have two versions in one JAR. This would further impede adoption. > This has been one of my concerns about A. Multirelease jars make a solution possible, but it is still a lot of headache for the library owner to build them (I assume I would need to branch or use a preprocessor of some kind). I think B or B+ is what we want.
