ChenSammi commented on pull request #2018:
URL: https://github.com/apache/ozone/pull/2018#issuecomment-796544221


   Current applications which depend on ozone modules,  if they don't upgrade 
ozone module version,  they need to do nothing.  
   If they want to upgrade ozone module version, say from 1.0.0 to 1.1.0,  they 
have to change ozone module groupId from "org.apache.org" to "org.apache.ozone" 
at the same time,  otherwise there will be maven module not found error.  
   
   @ayushtkn  do you think it's a big problem for current user? 


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



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

Reply via email to