chucheng92 opened a new issue, #4100:
URL: https://github.com/apache/incubator-seatunnel/issues/4100

   ### Search before asking
   
   - [X] I had searched in the 
[feature](https://github.com/apache/incubator-seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22)
 and found no similar feature requirement.
   
   
   ### Description
   
   When building SeaTunnel the output both on the command line and in IDEs like 
IntelliJ always show the artifact name as the module name.
   
   By simply setting a more human readable module name in all of the pom.xml 
files the build output becomes much easier to read for developers. Just like 
Apache Beam or Apache Flink etc.
   
   Also, changing the names do not change anything for users because 
dependencies are referred to by group/artifactId.
   
   before:
   [INFO] Reactor Summary for SeaTunnel 2.3.1-SNAPSHOT:
   [INFO] 
   [INFO] SeaTunnel .......................................... SUCCESS [  5.748 
s]
   [INFO] seatunnel-shade .................................... SUCCESS [  0.508 
s]
   [INFO] seatunnel-jackson .................................. SUCCESS [  3.574 
s]
   [INFO] seatunnel-common ................................... SUCCESS [  6.299 
s]
   [INFO] seatunnel-api ...................................... SUCCESS [  6.732 
s]
   [INFO] seatunnel-plugin-discovery ......................... SUCCESS [  2.462 
s]
   [INFO] seatunnel-core ..................................... SUCCESS [  0.365 
s]
   [INFO] seatunnel-core-starter ............................. SUCCESS [  2.209 
s]
   [INFO] seatunnel-translation .............................. SUCCESS [  0.354 
s]
   [INFO] seatunnel-translation-base ......................... SUCCESS [  1.225 
s]
   [INFO] seatunnel-translation-flink ........................ SUCCESS [  0.318 
s]
   [INFO] seatunnel-translation-flink-13 ..................... SUCCESS [  2.296 
s]
   [INFO] seatunnel-flink-starter ............................ SUCCESS [  2.113 
s]
   
   after:
   
   [INFO] SeaTunnel : .............................................. SUCCESS [ 
3.132 s]
   [INFO] SeaTunnel : Common ................................. SUCCESS [  6.332 
s]
   [INFO] SeaTunnel : Api .................................... SUCCESS [  6.729 
s]
   [INFO] SeaTunnel : Plugin Discovery ....................... SUCCESS [  2.491 
s]
   [INFO] SeaTunnel : Core : ................................. SUCCESS [  0.384 
s]
   [INFO] SeaTunnel : Core : Starter ......................... SUCCESS [  2.280 
s]
   [INFO] SeaTunnel : Translation : .......................... SUCCESS [  0.347 
s]
   [INFO] SeaTunnel : Translation : Base ..................... SUCCESS [  1.264 
s]
   [INFO] SeaTunnel : Translation : Flink : .................. SUCCESS [  0.314 
s]
   [INFO] SeaTunnel : Translation : Flink : 1.3 .............. SUCCESS [  2.127 
s]
   [INFO] SeaTunnel : Core : Flink Starter ................... SUCCESS [  1.963 
s]
   [INFO] SeaTunnel : Core : Flink Starter : 1.3 ............. SUCCESS [  3.615 
s]
   [INFO] SeaTunnel : Translation : Flink : 1.5 .............. SUCCESS [  2.576 
s]
   [INFO] SeaTunnel : Core : Flink Starter : 1.5 ............. SUCCESS [  2.726 
s]
   [INFO] SeaTunnel : Translation : Spark : .................. SUCCESS [  0.327 
s]
   [INFO] SeaTunnel : Translation : Spark : 2.4 .............. SUCCESS [  4.505 
s]
   [INFO] SeaTunnel : Core : Spark Starter : ................. SUCCESS [  1.573 
s]
   [INFO] SeaTunnel : Core : Spark Starter : 2.4 ............. SUCCESS [  3.245 
s]
   [INFO] SeaTunnel : Translation : Spark : 3.3 .............. SUCCESS [  3.536 
s]
   
   ### Usage Scenario
   
   maven build log or IDEA GUI, make more human-readable.
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to