ptlrs opened a new pull request, #8129:
URL: https://github.com/apache/ozone/pull/8129

   Please describe your PR in detail:
   When compiling with maven, the summary at the end shows that most module 
names have the prefix Apache Ozone .
    
   ```
   [INFO] Apache Ozone HDDS Hadoop Server dependencies ....... SUCCESS [  0.482 
s]
   [INFO] Apache Ozone HDDS RocksDB Tools .................... SUCCESS [  0.362 
s]
   [INFO] RocksDB Checkpoint Differ .......................... SUCCESS [  0.599 
s]
   [INFO] Apache Ozone HDDS Server Framework ................. SUCCESS [  2.509 
s]
   [INFO] Apache Ozone/HDDS Documentation .................... SUCCESS [ 51.698 
s]
   [INFO] Apache Ozone HDDS Container Service ................ SUCCESS [  2.711 
s] 
   ```
   Two modules do not follow the standard:
   ```
   # notice the extra `/`
     <name>Apache Ozone/HDDS Documentation</name> 
     <description>Apache Ozone/HDDS Documentation</description> 
   
   # no "Apache Ozone" prefix
     <name>RocksDB Checkpoint Differ</name> 
     <description>RocksDB Checkpoint Differ</description>  
   ```
   
   This PR standardizes the module names
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-12661
   
   ## How was this patch tested?
   CI: https://github.com/ptlrs/ozone/actions/runs/13997984010
   ```java
   [INFO] Apache Ozone Checkpoint Differ for RocksDB ......... SUCCESS [  0.706 
s]
   [INFO] Apache Ozone HDDS Server Framework ................. SUCCESS [  2.215 
s]
   [INFO] Apache Ozone Documentation ......................... SUCCESS [  3.868 
s]
   ```


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to