apache / apache/dubbo

[Bug] dubbo3.3.0, revision parameter of interface metadata, come from pom.xml's ${project.parent.version} instead of ${project.version}

Open
#14,728 2 comments 0 reactions 0 assignees View on GitHub
component/need-triage type/need-triage
Dominant language
Java
Stars
41.6k
Forks
26.4k
Avg merge
15h 13m
Merged PRs (30d)
4

Description

### Pre-check

- [X] I am sure that all the content I provide is in English.

### Search before asking

- [X] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues.

### Apache Dubbo Component

Java SDK (apache/dubbo)

### Dubbo Version

dubbo java 3.3.0, jdk 17, linux

### Steps to reproduce this issue

i package a spring boot jar, named: dubbo-samples-spring-boot-provider-2.0.jar
and pom.xml of this jar (location: META-INF\maven\org.apache.dubbo\dubbo-samples-spring-boot-provider\pom.xml)
as follows:
```xml

4.0.0


org.apache.dubbo
dubbo-samples-spring-boot
1.1
../pom.xml

dubbo-samples-spring-boot-provider
2.0

```
i opend the flag: dubbo.metadata-report.report-metadata: true
and when i start this jar, command like this:
java -jar dubbo-samples-spring-boot-provider-2.0.jar

it will report metadata to nacos, and nacos metadata like this:
![image](https://github.com/user-attachments/assets/0c0f75df-002a-4004-88eb-3b2652b6dbe9)

the param revision of serviceKey: test1/org.apache.dubbo.springboot.demo.DemoService:1.0:dubbo, is 1.1, why not 2.0 ?

### What you expected to happen

the revision param of interface, will it be better get from ${project.verion} of pom.xml ?

### Anything else

_No response_

### Are you willing to submit a pull request to fix on your own?

- [ ] Yes I am willing to submit a pull request on my own!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.