[
https://issues.apache.org/jira/browse/GROOVY-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029332#comment-18029332
]
Nicolas ROUSSET commented on GROOVY-9126:
-----------------------------------------
As [~primo.modica] mentioned more than 5 years ago, the issue still exists in
2.4.x.
Version 2.4.21 is actually the one where a project like Jenkins is stuck to
(for some reasons).
It would be really nice and useful to get a patch for 2.4.x.
> Unreachable line numbers after ARETURN in bytecode
> --------------------------------------------------
>
> Key: GROOVY-9126
> URL: https://issues.apache.org/jira/browse/GROOVY-9126
> Project: Groovy
> Issue Type: Bug
> Components: bytecode
> Affects Versions: 2.5.5, 2.5.6, 2.5.7
> Reporter: Adam Estabrook
> Assignee: Daniel Sun
> Priority: Major
> Fix For: 2.5.9, 3.0.0-rc-2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Starting with Groovy 2.5.5, unreachable line numbers were added to the byte
> code. This causes tools like JaCoCo to report uncovered lines. Removing these
> line numbers after the ARETURN would be helpful.
> [https://github.com/jacoco/jacoco/issues/884]
> ARETURN
> L1
> LINENUMBER 16 L1 <-- new line number that cant be hit after ARETURN
> FRAME FULL [] [java/lang/Throwable]
> NOP
> ATHROW
> LOCALVARIABLE this Lcom/company/Form; L0 L1 0
> MAXSTACK = 2
> MAXLOCALS = 1
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
