Business requirements for incompatible -source/-target/-bootclasspath values for Java builds

[Irina Iancu]

Hello Bazel Java users,

I'm working on migrating the Java rules to using platform-based toolchains. The current proposal is Migrate Java toolchains to platforms. Currently in a java_toolchain you can set source_version, target_version and bootclasspath. I'm wondering if you know of or have build requirements such that these three values are not compatible? Is there a need to define fine-grained toolchains for different source and target Java version? I'd expect this to be an exception, but I want to hear from you more.

Thanks,

Irina

[Gunnar Wagenknecht]

Hi Irina,

The only time I remember needing this was when we migrated the Equinox OSGi (and Eclipse Platform) code base from 1.4 to 1.5. It allowed us to use new Java 5 constructs in the source code (i.e. generics) and produce 1.4 output for backwards compatibility.

Honestly, this was a very specific use case back then. There might be a future need given the pace of Java's movement. However, I would questions this as a business requirement for Bazel.

-Gunnar

-- 
Gunnar Wagenknecht
gun...@wagenknecht.org, http://guw.io/

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAEwuVB33E7XeDQJiUNQ5afTzRRJKfxk7eqMwsLE1hxL98rtYFg%40mail.gmail.com.