Re: Re: Re: Release of ASM4

On Sat, Jul 30, 2011 at 7:24 AM, Rémi Forax <[email protected]> wrote:
> On 07/30/2011 03:43 PM, Eugene Kuleshov wrote:
>>
>>   It is also a good time to change the package name. The API has
>> changed significantly and there is enough of earlier versions of ASM
>> around used by various libraries to create conflicts.
>>
>>   regards,
>>   Eugene
>
> Hi Eugene,
> I know that you really want to change the package name
> but talking with several users at the JVM Summit last week,
> the idea is not popular.
> Most of them either manage their dependencies to have only
> jars that use one version of ASM (maven to the rescue)
> or they use jarjar.
>
> Also some Oracle guys say that they may want to include ASM next
> as an internal dependency of the JDK 8 using jigsaw,
> the default module system that will be introduce in JDK 8.
> Knowing that this module system will resolve all the dependency problems
> we currently have, I think it's better to wait now and come
> with two versions (one still 1.3 compatible and one 1.8 +module compatible)
> for the next release.
>
> Rémi

I would strongly prefer using different package name.
Also, relying on something Oracle may or may not get done seems bit
pre-mature at this point, especially if it would only help with new
JVMs.

Personally I am ok either wa, as I tend to shade ASM anyway to remove
chance of version conflict.
But developers who include ASM via references will be ill-served by
reusing same package name for incompatible versions, especially when
using Maven.

-+ Tatu +-

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