The naming convention for packages says it should be based on your companies domain name, so regardless of other issues you should probably change it anyway. If you don't you'll run into issues when both your version and the original version are on the classpath.
If you are planning to redistribute your fork to others you should be clear about where it's from and avoid confusion. You do imply endorsement if you keep the name, but it's also confusing for the users of the library if they can't tell them apart when googling and in stacktraces. (If you're just creating a private fork with minor changes you could consider not to bother...)
发布评论
评论（1）
包的命名约定表示它应该基于您的公司域名，因此无论其他问题如何，您都应该更改它。如果不这样做，当您的版本和原始版本都位于类路径上时，您就会遇到问题。
如果您打算将您的分叉重新分发给其他人，您应该清楚它的来源并避免混淆。如果你保留这个名字，你确实暗示了认可，但如果库的用户在谷歌搜索和堆栈跟踪中无法区分它们，这也会让库的用户感到困惑。 （如果您只是创建一个带有微小更改的私人分叉，您可以考虑不要打扰......）
The naming convention for packages says it should be based on your companies domain name, so regardless of other issues you should probably change it anyway. If you don't you'll run into issues when both your version and the original version are on the classpath.
If you are planning to redistribute your fork to others you should be clear about where it's from and avoid confusion. You do imply endorsement if you keep the name, but it's also confusing for the users of the library if they can't tell them apart when googling and in stacktraces. (If you're just creating a private fork with minor changes you could consider not to bother...)