On Wed, Mar 25, 2015 at 7:55 AM, nicolas de loof <[email protected]> wrote: > new programmation options, not just new filesystem API (that we use via > XMLFile anyway)
To be clear, there is code scattered all over Jenkins core (and some plugins) which would benefit significantly from java.nio.file. (In a few such cases we are actually already using Java 7 APIs via reflection when available. In most cases we are not because it is too painful.) BTW a much more conservative proposal was made (by me?) a few months ago: that the Jenkins (core + plugin) _build requirement_ be switched to JDK 7+. src/main/java/ would remain compiled with -source 6 (so no <>, try-with-resources, etc.) but could use Java 7-only APIs without reflection, only guarded by Animal Sniffer (isolated in methods marked @IgnoreJRERequirements). Doing that for JDK 8 is not terribly useful since so many of the new APIs require -target 8. It was also proposed that src/test/java/ could switch to -source 8 and use Java 8 APIs, to make writing tests more pleasant even when the main sources are stuck on 6, though it has since been pointed out that while Maven supports this style without issue, IntelliJ cannot handle it. (NetBeans handles it; not sure about Eclipse.) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1QwEFNwWAUb72CaoFj99WHi%2BjyVdr%3DCs3UMAW1Uzib6w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
