baidu / baidu/Jprotobuf-rpc-socket
3.5.3依赖jprotobuf-jre:1.0.0会导致jar包冲突
- Dominant language
- Java
- Stars
- 535
- Forks
- 216
- PR merge metrics
- No merged PRs in 30d
Description
```
+--- com.baidu:jprotobuf-rpc-registry-redis:3.5.3
| +--- com.baidu:jprotobuf-rpc-core-spring:3.5.3
| | +--- com.baidu:jprotobuf-rpc-core:3.5.3
| | | +--- com.baidu:jprotobuf-rpc-core-test:3.5.3
| | | | +--- org.springframework:spring-web:3.2.11.RELEASE -> 4.2.7.RELEASE (*)
| | | | +--- junit:junit:4.10 -> 4.12
| | | | | \--- org.hamcrest:hamcrest-core:1.3
| | | | +--- com.baidu:jprotobuf-jre:1.0.0
```
如果我在项目中引入com.baidu:jprotobuf:2.0.7 有可能会导致jar包冲突，2.0.7中的FieldType比jprotobuf-jre:1.0.0中多了MAP这个枚举
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the dependency tree shown for com.baidu:jprotobuf-rpc-registry-redis:3.5.3 and compare com.baidu:jprotobuf-jre:1.0.0 with com.baidu:jprotobuf:2.0.7. Confirm whether the differing FieldType enum, including MAP, causes the reported jar conflict and define a dependency arrangement that avoids it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100