[
https://issues.apache.org/jira/browse/BEAM-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939315#comment-16939315
]
Lukasz Gajowy commented on BEAM-8021:
-------------------------------------
Thank you [~preston] for reporting this. According to my knowledge, we do not
need to publish build-tools to be able to depend on it but I may be missing
something of course. Unfortunately, I was not able to reproduce this. So far I
tried to run:
{code:java}
./gradlew clean build -p runners/flink {code}
and it succeeded. I also tried to remove all build-tools jars from my local
caches and it still succeeded. Could you provide steps to reproduce the issue
locally?
> Add Automatic-Module-Name headers for Beam Java modules
> --------------------------------------------------------
>
> Key: BEAM-8021
> URL: https://issues.apache.org/jira/browse/BEAM-8021
> Project: Beam
> Issue Type: Sub-task
> Components: build-system
> Reporter: Ismaël Mejía
> Assignee: Lukasz Gajowy
> Priority: Minor
> Fix For: 2.17.0
>
> Time Spent: 8h
> Remaining Estimate: 0h
>
> For compatibility with the Java Platform Module System (JPMS) in Java 9 and
> later, every JAR should have a module name, even if the library does not
> itself use modules. As [suggested in the mailing
> list|https://lists.apache.org/thread.html/956065580ce049481e756482dc3ccfdc994fef3b8cdb37cab3e2d9b1@%3Cdev.beam.apache.org%3E],
> this is a simple change that we can do and still be backwards compatible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
