-
Notifications
You must be signed in to change notification settings - Fork 277
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
Fix Java8 instrumentation exception due to use of ASM4 API version. #299
Conversation
Fix Java8 instrumentation exception due to use of ASM4 API version.
@christ66 : When this fix gonna be release? Please confirm. |
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). |
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. |
I'm also awaiting the new build like a child on a 24/12. |
@christ66 : Can you give me the latest release version to pull and see if it works? |
We need a release, please! |
a release would be cool, yeah. :) |
+1 |
the maven plugin need to be updated to reflect |
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? |
Is there an ETA for the 2.1.2 release already? |
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? |
Is there an ETA for the 2.1.2 release already? |
2.1.2 being released anytime soon? This is breaking us from using cobertura. |
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? |
I am stuck with the same issue. Seems new release will fix this issue. Anyone working to release a new version? |
Me too, can anyone release a new version? The latest version |
Hi everyone! We can release within two weeks. A snapshot release was issued a few months ago. Best! |
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? |
Hi, any latest development on this request? |
what happened? still no news? |
Fix #248 exception at instrumentation phase. No special handling logic for new API version is needed.