nielsbasjes opened a new pull request #12907:
URL: https://github.com/apache/flink/pull/12907
## What is the purpose of the change
Make the build output more human readable for the developers van various
situations.
## Brief change log
Add or change the `<name>` of each maven module (i.e. in every pom.xml)
## Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
The simplest way to test is by doing a `mvn clean` and verify the list of
names at the end looks good.
Also looking at the change set verify that the names for each module are
correct.
In some exceptional cases I made the name reflect a bit more the purpose
like in the case of
`flink-examples/flink-examples-build-helper` where the description indicates
`This is a utility module for building example jars to be used in flink-dist.`
so I named it `Flink : Examples : Dist : `
Fun fact: I noticed that the ordering of the modules during the build is
changed a lot by maven because apparently the ordering of the modules in the
pom.xml does not meet the configured dependencies between the modules. So maven
reorders the build by itself.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): **no**
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: **no**
- The serializers: **no**
- The runtime per-record code paths (performance sensitive): **no**
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: **no**
- The S3 file system connector: **no**
## Documentation
- Does this pull request introduce a new feature? **no**
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
