Adding asm to JDK 8

[Brian Goetz]

The current plan is to use ASM long-term to generate classes at runtime. 
  Now, it is possible that "something better will come along" (perhaps 
needed functionality will be provided by JSR-292 in the future) but 
we're not banking on this.

The EE team has also asked that we officially include ASM in the base 
distribution, so they can get rid of the seven copies of ASM that are 
floating around in Glassfish.

My thinking was that the base module would have a private 
(non-exporting) dependency on ASM, so that even though the language 
runtime uses ASM, users only get it when they ask for it.

For now the packages have been renamed but once we modularize ASM we may 
not need to do that any more.

On 2/3/2012 6:46 AM, Alan Bateman wrote:
> On 03/02/2012 04:04, Mandy Chung wrote:
>> Great. That would give a good starting point.
>>
>> Mandy
>>
>> On 2/2/2012 7:34 PM, Brian Goetz wrote:
>>> The main ASM distribution is broken into 5 jars, based on how people
>>> tend to use it; this is probably a good starting candidate for module
>>> boundaries.
> Brian - I also think we'll need a brief overview on usage too. In
> particular, is the plan to run ASM at runtime and is this the plan for
> the long term too or will it be replaced by something in the core to
> generate the classes as runtime? (I'm been too busy to track many of the
> details of lambda).
>
> -Alan