-
Notifications
You must be signed in to change notification settings - Fork 26.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't compile under JDK 1.9, caused by an invalid import. #1116
Comments
It will be resolved in next release , please add fake class to compile |
You also could remove some test cases , sorry for careless :( |
mercyblitz
added a commit
to mercyblitz/dubbo
that referenced
this issue
Dec 26, 2017
chickenlj
pushed a commit
that referenced
this issue
Jan 22, 2018
* Fixed #1116 #1120 #1121 #1122 #1141 #1125 * DubboConfigConfiguration's Single and Multiple to be public classes * @DubboComponentScan is compatible with Spring @service completely * @service and @reference issues on <dubbo:annotation> * To fix an issue on <dubbo:annotation> when id attribute is absent * To change the prefixes of properties when @EnableDubboConfig binds multiple Config Bean
It's been fixed |
rolandhe
pushed a commit
to rolandhe/dubbo
that referenced
this issue
Sep 9, 2019
* Fixed apache#1116 apache#1120 apache#1121 apache#1122 apache#1141 apache#1125 * DubboConfigConfiguration's Single and Multiple to be public classes * @DubboComponentScan is compatible with Spring @service completely * @service and @reference issues on <dubbo:annotation> * To fix an issue on <dubbo:annotation> when id attribute is absent * To change the prefixes of properties when @EnableDubboConfig binds multiple Config Bean
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
com.alibaba.dubbo.config.spring.context.annotation.provider里面
import com.sun.org.apache.regexp.internal.RE无效导入JDK9下部能编译通过
同时下面两个也是无效导入
import com.alibaba.dubbo.rpc.Protocol;
import org.springframework.context.annotation.ImportResource;
The text was updated successfully, but these errors were encountered: