[
https://issues.apache.org/jira/browse/HADOOP-18916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773237#comment-17773237
]
ASF GitHub Bot commented on HADOOP-18916:
-----------------------------------------
pjfanning commented on PR #6131:
URL: https://github.com/apache/hadoop/pull/6131#issuecomment-1752758127
@ayushtkn the thing is that more and more jars are having module-info
classes added to them. To have the hadoop build choose 2 sets of coordinates
and ignore the rest seems like a bad idea.
I've wasted tonnes of time on 3.3 builds recently and am not going to spend
any more time on them.
> module-info classes from external dependencies appearing in uber jars
> ---------------------------------------------------------------------
>
> Key: HADOOP-18916
> URL: https://issues.apache.org/jira/browse/HADOOP-18916
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Reporter: PJ Fanning
> Priority: Major
> Labels: pull-request-available
>
> hadoop-client-minicluster and hadoop-client-runtime try unsuccessfully to
> exclude module-info classes from dependencies. Over time, more and more jars
> have these classes.
> The module-info classes are causing issue with CI builds. Builds can fail if
> there are more than module-inf class that is not excluded.
> It seems better to exclude them all, especially since they will be affected
> by shading anyway.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
