Maven and Ant are a couple places that likely needed custom solutions, but probably not applicable here. Maybe something in Commons? I tried looking at a few random projects, but I'm not seeing anything. Spring Framework might have something.
On Sun, 17 May 2020 at 13:03, Volkan Yazıcı <[email protected]> wrote: > > Maybe a naive question, but... Does anybody know how other Apache > projects deal with this? Do they also require multiple JDKs to be > present at compile time? Do they also employ `java9` directory work > arounds as in log4j? > > On Sat, Apr 11, 2020 at 6:39 PM Matt Sicker <[email protected]> wrote: > > > > I was playing around with the pom a little bit yesterday when I came > > across a relatively new maven-compiler-plugin configuration element > > called <multiReleaseOutput> which can be used to output the compiled > > classes relative to META-INF/versions/N rather than the root. This > > looks like it would likely remove the need to use > > maven-assembly-plugin as an intermediary step. > > > > I found an interesting approach linked in [1] as the multi-release > > parent strategy with source code at [2]. I attempted to refactor > > log4j-api to use this pattern, but I couldn't figure out how to make > > the same pattern work for test classes (which made it impossible to > > compile log4j-api/src/test/java9). > > > > I'm going to continue experimenting a bit with this, but has anyone > > tried out the more recent multi-version tooling support? We were early > > users of some things, so I'd imagine tooling has caught up by now. > > > > [1]: > > https://maven.apache.org/plugins/maven-compiler-plugin/multirelease.html > > [2]: https://github.com/meterware/multirelease-parent/blob/master/pom.xml > > > > -- > > Matt Sicker <[email protected]> -- Matt Sicker <[email protected]>
