[
https://issues.apache.org/jira/browse/GROOVY-9610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Primo Modica updated GROOVY-9610:
---------------------------------
Description:
This ticket is the same of GROOVY-9126 but for a different groovy version.
>From the above ticket:
{noformat}
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
{noformat}
The problem is that the bug has been introduced in GROOVY-7647 where fix
version/s are **
[2.4.16|https://issues.apache.org/jira/issues/?jql=project+%3D+GROOVY+AND+fixVersion+%3D+2.4.16],
[3.0.0-alpha-4|https://issues.apache.org/jira/issues/?jql=project+%3D+GROOVY+AND+fixVersion+%3D+3.0.0-alpha-4],
[2.5.5|https://issues.apache.org/jira/issues/?jql=project+%3D+GROOVY+AND+fixVersion+%3D+2.5.5]
Request:
Please fix also versions > 4.4.16
was:
This ticket is the same of
[GROOVY-9126|https://issues.apache.org/jira/browse/GROOVY-9126] but for a
different groovy version.
>From the above ticket:
{noformat}
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
{noformat}
The problem is that the bug has been introduced in [GROOVY-7647
|https://issues.apache.org/jira/browse/GROOVY-7647] where fix version/s are **
[2.4.16|https://issues.apache.org/jira/issues/?jql=project+%3D+GROOVY+AND+fixVersion+%3D+2.4.16],
[3.0.0-alpha-4|https://issues.apache.org/jira/issues/?jql=project+%3D+GROOVY+AND+fixVersion+%3D+3.0.0-alpha-4],
[2.5.5|https://issues.apache.org/jira/issues/?jql=project+%3D+GROOVY+AND+fixVersion+%3D+2.5.5]
Request:
Please fix also versions > 4.4.16
> Unreachable line numbers after ARETURN in bytecode
> --------------------------------------------------
>
> Key: GROOVY-9610
> URL: https://issues.apache.org/jira/browse/GROOVY-9610
> Project: Groovy
> Issue Type: Bug
> Components: bytecode
> Affects Versions: 2.4.17
> Reporter: Primo Modica
> Priority: Major
> Labels: bytecode, jacoco
>
> This ticket is the same of GROOVY-9126 but for a different groovy version.
> From the above ticket:
> {noformat}
> 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
> {noformat}
> The problem is that the bug has been introduced in GROOVY-7647 where fix
> version/s are **
> [2.4.16|https://issues.apache.org/jira/issues/?jql=project+%3D+GROOVY+AND+fixVersion+%3D+2.4.16],
>
> [3.0.0-alpha-4|https://issues.apache.org/jira/issues/?jql=project+%3D+GROOVY+AND+fixVersion+%3D+3.0.0-alpha-4],
>
> [2.5.5|https://issues.apache.org/jira/issues/?jql=project+%3D+GROOVY+AND+fixVersion+%3D+2.5.5]
> Request:
> Please fix also versions > 4.4.16
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
