You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The groupId currently used by the logging module in RocketMQ is not very neutral, and some developers from the community have suggested that we move it under the groupId of org.apache.rocketmq. There are two potential solutions available:
The first solution is to establish a new repository called rocketmq-logging, while the second solution is to place it in rocketmq-external.
The logging module has the following characteristics: the shaded logback is not universal and is specifically shaded for RocketMQ. this is a project customized for the RocketMQ main repository. However, Maven multi-module projects are not very friendly towards the independent shaded modules, so it is not very suitable to have it in the RocketMQ main repository.
Additionally, since ASF repositories cannot be deleted and can only be archived, we need to carefully consider this to avoid unnecessary archiving operations in the future. for example: rocketmq-client-rust
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The groupId currently used by the logging module in RocketMQ is not very neutral, and some developers from the community have suggested that we move it under the groupId of
org.apache.rocketmq
. There are two potential solutions available:The first solution is to establish a new repository called rocketmq-logging, while the second solution is to place it in rocketmq-external.
The logging module has the following characteristics: the shaded logback is not universal and is specifically shaded for RocketMQ. this is a project customized for the RocketMQ main repository. However, Maven multi-module projects are not very friendly towards the independent shaded modules, so it is not very suitable to have it in the RocketMQ main repository.
Additionally, since ASF repositories cannot be deleted and can only be archived, we need to carefully consider this to avoid unnecessary archiving operations in the future. for example: rocketmq-client-rust
Beta Was this translation helpful? Give feedback.
All reactions