Adding asm to JDK 8

[Phil Race]

On 2/3/2012 9:38 AM, Brian Goetz wrote:
> Lambda was the proximate driving force.  EE was also a contributor; as 
> I mentioned earlier, Glassfish includes half a dozen versions of ASM, 
> some of different vintages, because of how it is componentized.
>
> We can probably get rid of the extra repo once we can make it into a 
> module.

Why does it need to be a module before that can happen ?
So far as I can tell initially binary goes into rt.jar either way 
(source in shared or separate repo).

-phil.

>
> On 2/3/2012 12:11 PM, Phil Race wrote:
>> Oh, its for lambda! Thank you for mentioning that. I had no clue what we
>> needed this thing for :-), may be it was obvious to the rest of the 
>> world
>> but not to me and I was surprised it wasn't mentioned in Jim's email.
>>
>> But does it really need its own new repo ? I think there needs to be a
>> discussion on this
>> as I'd like to see *fewer* of them. How enormous is this thing ?
>>
>> Can't be that big if there's a copy buried in jax-ws
>>
>> -phil.
>>
>> On 2/3/2012 3: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
>>