[
https://issues.apache.org/jira/browse/GROOVY-9315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981215#comment-16981215
]
Eric Milles commented on GROOVY-9315:
-------------------------------------
That place should be CompilerConfiguration.setTargetBytecode. This is what
Ant, Gradle or Maven are setting when user indicates a release/source/target
property.
What is the difference between "parse mode" and "compute mode"?
"old codebase" is just "codebase"
Can this wait for Groovy 3.0.1 or Groovy 4?
> Bump bytecode version to 1.8
> ----------------------------
>
> Key: GROOVY-9315
> URL: https://issues.apache.org/jira/browse/GROOVY-9315
> Project: Groovy
> Issue Type: Improvement
> Reporter: Daniel Sun
> Assignee: Daniel Sun
> Priority: Major
> Fix For: 3.0.0-rc-2
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Groovy 3.0.0 requires Java 8+ and supports Java8 language features, so it's
> better to use its relevant class file version, i.e. 1.8
> In the old codebase, we can not manage the bytecode version well, for
> example, we use many bytecode versions to generate bytecode, some very old
> bytecode versions like {{1.3}} are still used.
> What I propose to do is manage the default bytecode code version in a place,
> same for its relevant compute mode and parse mode. If we want to change them,
> just modify only one place.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
