2. Shall we need to change all the java package name to org.apache.* ? If
do this, users will encounter the upgrading problem.


The current package is com.alibaba.dubbo right?  Unfortunately this puts us
into a "you have to rename it" situation.  Including the company name in
the package is a problem for our branding/trademarks.

3. Now, our groupId is "com.alibaba", shall we need to change it to
"org.apache"?


Most projects follow a "org.apache.projectName" naming scheme.  So
org.apache.dubbo would be expected.


Considering that a large number of users already use dubbo,Changing the name of 
the package can lead to breaking the compatibility.

for case 1:  New users use dubbo, we should do nothing.


case 2:     The user is convenient to upgrade dubbo to apache version( change 
com.alibaba.xxx to com.apache.xx),  consumer and server upgrades at the same 
time.

We can provide tools to automatically convert the package name, the name of the 
extension interceptor, the package name of the xml configuration, etc.

case 3:   The user is convenient to upgrade dubbo to apache version( change 
com.alibaba.xxx to com.apache.xx),  consumer and server can't upgrades at the 
same time.

This scenario is the most complicated, we should be compatible at the source 
code level,and prompting future versions will remove the compatible code. It is 
recommended that you use this tool to manually convert old code.

Reply via email to