[jira] [Comment Edited] (FLINK-17059) flink-shaded-hadoop-2-uber:2.8.3-10.0 has invalid pom in Gradle

["Chesnay Schepler (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-17059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078985#comment-17078985 ] 

Chesnay Schepler edited comment on FLINK-17059 at 4/9/20, 6:48 AM:
-------------------------------------------------------------------

[~johnlon] flink-shaded 11 hasn't been released yet. As an intermediate workaround, you can checkout the [flink-shaded|https://github.com/apache/flink-shaded/commits/master] master, build/install it, and direct Flink to work against this version by specifying \{{-Dflink.shaded.version=11.0}} when building Flink.


was (Author: zentol):
[~johnlon] flink-shaded 11 hasn't been released yet. As an intermediate workaround, you can checkout the [flink-shaded|https://github.com/apache/flink-shaded/commits/master] master, build/install it, and direct Flink to work against this version by specifying {{-Dflink.shaded.version=11.0 }}when building Flink.

> flink-shaded-hadoop-2-uber:2.8.3-10.0 has invalid pom in Gradle
> ---------------------------------------------------------------
>
>                 Key: FLINK-17059
>                 URL: https://issues.apache.org/jira/browse/FLINK-17059
>             Project: Flink
>          Issue Type: Bug
>          Components: BuildSystem / Shaded
>    Affects Versions: shaded-10.0
>            Reporter: John Lonergan
>            Priority: Major
>
> The uploaded pom for flink-shaded-hadoop-2-uber:2.8.3-10.0 has invalid pom 
> has a variable in the artefact version field.
> That version is being populated from the parent pom where hadoop.version=2.4.1
> This means the then internal model for this pom when it's loaded says its v 2.4.1 but the external file version says 2.8.3
> This means that when Gradle loads the artefact it barfs about bad metadata and refuses the artefact.
> Can't use this series of jars in gradle - except for the actual 2.4.1 instance.
> Easy to reproduce - just create a gradle dependency on the 2.8.3 variant.
> --
> I guess this situation might be on in mvn??
> Suggest a test is added that attempts to consume these artefacts in other common build tools.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)