Re: CompilierConfiguration#CURRENT_JVM_VERSION

2018-05-15 Thread Remko Popma
+1 On Tue, May 15, 2018 at 7:01 PM, Paul King wrote: > > Hi all, > > In CompilerConfiguration we have a public constant CURRENT_JVM_VERSION > which actually represents the minimum JDK version supported by a particular > version of Groovy (potentially on a particular VM runtime). I was thinking >

Re: CompilierConfiguration#CURRENT_JVM_VERSION

2018-05-15 Thread John Wagenleitner
+1 for deprecating the current constant and new name (see note below). If the new constant wont be used internally then I might suggest no new constant is created. Else if it's created in order to provide an alternate to the deprecated one, would it make sense to provide it via `groovy.lang.Groovy

Re: CompilierConfiguration#CURRENT_JVM_VERSION

2018-05-15 Thread Daniel.Sun
+1 Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

CompilierConfiguration#CURRENT_JVM_VERSION

2018-05-15 Thread Paul King
Hi all, In CompilerConfiguration we have a public constant CURRENT_JVM_VERSION which actually represents the minimum JDK version supported by a particular version of Groovy (potentially on a particular VM runtime). I was thinking of deprecating above constant (it's not used in the Groovy codebase)