Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Java8 instrumentation exception due to use of ASM4 API version. #299

Merged

Conversation

vkovalchuk
Copy link

Fix #248 exception at instrumentation phase. No special handling logic for new API version is needed.

christ66 added a commit that referenced this pull request Mar 14, 2016
Fix Java8 instrumentation exception due to use of ASM4 API version.
@christ66 christ66 merged commit cc1a4ed into cobertura:master Mar 14, 2016
@Saiftari
Copy link

Saiftari commented Jun 8, 2016

@christ66 : When this fix gonna be release? Please confirm.

@vkovalchuk vkovalchuk deleted the fix-java8-instrumentation-asm5 branch June 8, 2016 18:31
@aaime
Copy link

aaime commented Jun 20, 2016

Yep, a release would be much welcomed, right now cannot do coverage checks (well, one can use jacoco as an alternative, but I'd rather not, it's more invasive than cobertura build wise).

@christ66
Copy link
Member

A release will be done soon (probably next weekend). I would like to write more java 8 specific unit tests to make sure there is no issues with java 8.

@Tournemine
Copy link

I'm also awaiting the new build like a child on a 24/12.

@Saiftari
Copy link

Saiftari commented Jul 1, 2016

@christ66 : Can you give me the latest release version to pull and see if it works?

@RDevet
Copy link

RDevet commented Oct 14, 2016

We need a release, please!

@heidensi
Copy link

heidensi commented Nov 4, 2016

a release would be cool, yeah. :)

@jochenvdv
Copy link

+1

@erfangc
Copy link

erfangc commented Nov 22, 2016

the maven plugin need to be updated to reflect 2.1.2 as most people use cobertura via maven, currently even in 2.8-SNAPSHOT the maven plugin is still pointing to 2.1.1 https://github.com/mojohaus/cobertura-maven-plugin/blob/master/pom.xml#L135

@cverges-medallia
Copy link

The plugin cannot be updated until a cobertura-runtime release for 2.1.2 is pushed to Maven Central. Do we have an ETA for that?

@vrcca
Copy link

vrcca commented Feb 2, 2017

Is there an ETA for the 2.1.2 release already?

@xylo
Copy link

xylo commented Jun 8, 2017

Did I miss something? We are still waiting for a new release (2.1.2), although the bug was fixed half a year ago? Is there any useful workaround or is this project dead?

@marioplumbarius
Copy link

Is there an ETA for the 2.1.2 release already?

@tldavies
Copy link

2.1.2 being released anytime soon? This is breaking us from using cobertura.

@xylo
Copy link

xylo commented Aug 22, 2018

Since this fix has been merged on 14 Mar 2016 I wonder if the fixed version (2.1.2) will be still released in 2018? What is actually cobertura's release cycle for bug fix releases? 2, 5, or 10 years?

@codejayant
Copy link

I am stuck with the same issue. Seems new release will fix this issue. Anyone working to release a new version?

@VicZhang1
Copy link

Me too, can anyone release a new version? The latest version 2.1.1 is released in 2015.

@jmrozanec
Copy link
Member

Hi everyone! We can release within two weeks. A snapshot release was issued a few months ago. Best!

@codejayant
Copy link

Hi @jmrozanec, can you please let us know when the new release is coming up? Also can you please share the snapshot release detail and if it has the fix?

@codejayant
Copy link

Hi, any latest development on this request?

@binarywang
Copy link

what happened? still no news?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

INVOKESPECIAL/STATIC on interfaces require ASM 5