[fedora-java] Gradle upgrade issues (#976330)
mizdebsk at redhat.com
Tue Oct 22 08:29:36 UTC 2013
On 10/21/2013 09:23 PM, David Walluck wrote:
> On 10/21/2013 11:55 AM, Mikolaj Izdebski wrote:
>> yes, there are some version problems, most notably Objectweb ASM.
>> Different Gradle dependencies use versions 3 and 4 (shaded to avoid
>> namespace conflicts). Fedora does not allow bundled libraries, which
>> causes conflict between ASM 3 and 4. (Porting from ASM 3 to ASM 4 is
>> possible, but non-trivial as there were major changes. This would
>> again require some work.)
> I am not sure what you mean about asm. Fedora may not allow bundled
> libraries, but it may allow two versions of a library in the case of
> major incompatibility. The maven coordinates changed from 3 to 4, but
> unfortunately most of the class names did not, leading to serious
> problems if both versions are on the classpath at the same time. But,
> this doesn't mean that it has to be bundled.
Gradle uses some libraries, which use different incompatible versions of
ASM (3 and 4). For upstream that's not a problem as one copy of ASM is
shaded (bundled with namespace changed). In Fedora ASM cannot be shaded
as this would be against Fedora policy. This causes problems as two
versions of ASM end up being on Gradle classpath.
More information about the java-devel