Re: ASM 5.2 ?

Hi,

Apologies if this is slightly off topic.

*> jacoco/issues/177 <https://github.com/jacoco/jacoco/issues/177>*

With this issue I see the mention of
ClassWriter.getCommonSuperClass(Unknown Source) ... and the issue of ASM
needing to load classes to re-calculate the stack frames. As an ASM user
(for Ebean ORM) I hit this issue a lot and we try to ensure the agent has
access to the appropriate classpath such that it can load classes for
ClassWriter.getCommonSuperClass().

Sometimes depending on the context (more specifically enhancement running
as an IDE plugin for IDEA and Eclipse etc) it is hard to build and supply
this classpath for the agent/enhancement.

Is there a plan to remove this classpath requirement (ie. change the
implementation of ClassWriter.getCommonSuperClass() such that it doesn't
need the actual Classes) ?

If there was that would be very welcome indeed and yes I'd love to see a
5.2 release with that change.

Apologies if I have completely missed the topic here.


Cheers, Rob.


On 12 December 2016 at 03:53, Remi Forax <[email protected]> wrote:

> Hi Evgeny,
>
> ------------------------------
>
> *De: *"Evgeny Mandrikov" <[email protected]>
> *À: *"“[email protected]”" <[email protected]>
> *Envoyé: *Samedi 10 Décembre 2016 01:22:24
> *Objet: *[asm] ASM 5.2 ?
>
> 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?
>
>
> yes, some fixes from the trunk are not yet 'forward ported' to ASM6_FUTURE
> branch.
>
> So what do you think about release 5.2? Are there any plans?
>
>
> I think it's a good idea.
> Eric ?
>
> 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
>
>
> Rémi
>
>
>
>
> --
> 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
>
>
>
> --
> 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
>
>


-- 
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