ASM 5.2 ?

Evgeny Mandrikov <[email protected]> Sat, 10 Dec 2016 00:22:24 +0000
Newsgroups gmane.comp.java.objectweb.asm
Message-ID <CAEPFu6-riZh3UegfZ_6Doo=uFwp83w_NXfJXiWYk1rNhkxDd_w@mail.gmail.com>
Hi ASM developers,

Seems that trunk accumulated quite some changes without further activity
for couple of months since ASM version 5.1.
And they are interesting for ASM consumers, in particular for JaCoCo (
http://www.jacoco.org/jacoco/index.html ):
http://forge.ow2.org/tracker/?func=detail&aid=317630&group_id=23&atid=100023
 for https://github.com/jacoco/jacoco/issues/177
http://forge.ow2.org/tracker/?func=detail&aid=317748&group_id=23&atid=100023
 for https://github.com/jacoco/jacoco/issues/462
If my memory is correct, some are of an interest also for ByteBuddy (
http://bytebuddy.net/ ) that is nowadays used by Mockito (
http://mockito.org/ ) and Hibernate ( http://hibernate.org/ ).

I know that another thread discusses 6.0 alpha 2. While we can test it
(actually should and probably will), but it might be hard (maybe even
impossible) to ship into production release with dependency on alpha
version. Here I mostly think about Eclipse projects that require addition
of ASM into Eclipse Orbit ( https://www.eclipse.org/orbit/ ), in particular
EclEmma ( https://projects.eclipse.org/projects/technology.eclemma ) that
transitively uses ASM via JaCoCo. Also seems that 6.0 branch does not
contain some of the fixes that are present in trunk, isn't it?

So what do you think about release 5.2? Are there any plans?
If needed, then don't hesitate to ask for a help - for example we (JaCoCo
developers) can retest trunk and reach out developers of ByteBuddy and
Mockito to do the same. As well as promote 5.2 release to Eclipse Orbit.

Best regards,
Evgeny


-- 
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws